Skip to Content
Personal Insights

ByDesign SDK beginner issues and solutions

I found in SAP Community often that there are some common issues which many partners got when start using ByDesign and SDK.I’ve also experienced those things before and I think it would be helpful to summarize in one blog.Although not including all common issues, here are some with the solutions.

  1. XBO : UI Designer open message
  2. How to see which Business Object belongs to which UI name
  3. Technical error AP_ESI_COMMON 107
  4. How to use adaptation mode created fields in SDK
  5. Extension fields value are disappeared after created the Patch solution
  6. Dump Error:”No access possible via a ‘NULL’ data reference”
  7. Authorization role missing for service Service Interface xxxxxxxxx(Communication Arrangements Quick Guide)
  8. Adding Preview button and Preview > No PDF found. Invalid Form Template Group Code xxxxx. (Deploy Business Configuration)
  9. CSS Download Error

1. XBO : UI Designer open messasge

When you added extension field in standard BO and then try to enhence the standard screen,
you will got this message.
“Component which you are trying to edit comes from a lower layer.
Please use Extensibility Explorer to edit”
Sometimes may be you can get wrong idea from this message (just like me :D).
Its information message so just click OK and continue your enhancement.

 

2. How to see which Business Object belongs to which UI name

In the SDK Repository Explorer > Business Objects tab, there has a lot of standard BO you can see.
Its a bit difficult to know which WorkCenter belongs to which BO on system.
But you can know by checking this. “UI Text” of business object.
Eg: Here you can know Journal Entry Voucher of BO is “Accounting Entry”.

3. Technical error AP_ESI_COMMON 107

That error usually occur when there has logic written in standard events that update/inserting instance value when the document status is *NOT* in write-allowed state.
To avoid it, add the document status checking before the update/insert instance logic.

Eg:

// StatusCode 3 = Released
// if document is in Released status, skip the data assign logic
if(this.Status.ReleaseStatusCode != "3") {

	this.ExtensionField = "abc";

}

4. How to use adaptation mode created fields in SDK

Sometimes we’ve added the extension fields via Key User – Adaptation mode.
And then those fields need to use in SDK logic.
How can you call those in SDK script files?
Actually [SAP Cloud Applications Studio. pdf] have that contents and most just don’t notice it.

Find in the PDF with this keywords.
“Create References to Customer-Specific Fields”, “.ref”

5. Extension fields value are disappeared after created the Patch solution

You created a solution in Tenant A, have extension fields in it and data instance also created.
Then you downloaded the solution and deployed to another tenant (Test Tenant B or PRD).
When some fix is needed, you create the Patch in the test tenant A and
Patch became “Enabled” and Original solution became “Disabled” automatically.
So at that time, your old instances of original solution became disabled and the fields you are seeing now on UI screens are patch solution fields.
Actually the values are not disappeared. They are just being disabled.
If you want to see the value again, you can Enable the original solution and check.
In the SDK, under Administration menu, open “Implementation Manager”.
There you can disable/enable the solution.

6. Dump Error:”No access possible via a ‘NULL’ data reference”

This error usually occurs when you are accessing the value of the element in a Null node.
To solve it, put the null checking code before your data assignment logic.

Eg:

//If its 0~1 node, 
if(this.instance.IsSet()) {
	this.instance.ID.content = "abc";
}

//If its 0~n node,
if(this.node.Count() > 0) {
	var test = this.node.GetFirst().ID.content;
}

※You can know the exact error line info in the SDK, View menu, “Dump Analysis”.

7. Authorization role missing for service Service Interface xxxxxxxxx
(Communication Arrangements Quick Guide)

When you start using byD webservice and call it and can face this error.
Mostly this occurs because you haven’t complete the Communicaton System, Communication Arrangement setting for that webservice.
Referencing the SAP help docuemnt with key word “Communication Arrangements Quick Guide” could help this.

8. Adding Preview button and Preview > No PDF found. Invalid Form Template Group Code xxxxx.
(Deploy Business Configuration)

You have custom Form Template and Preview setting created in addon solution.
When you tried to preview it, will get No PDF Found error and preview failed.
It is because you haven’t deploy the Business Configuration in solution.

 

9. CSS Download Error

When you assemble and download the CSS and got the error like this,
it means some users are in that CSS and locked the files.
So, delete sessions, (log-out the SDK to be sure), then re-login and try again to download.

 

 

And below error happens when Incosistant items exist or some BCC files are not activated.

First, check whether all files are activated or not.
If all files are successfully activated, comapre the current solution contents and the last downloaded solution has incosistent items or not (check by developers).
If still cannot solve the error, raise incident to SAP.

Hope this helps.

Thanks,

May

 

 

 

5 Comments
You must be Logged on to comment or reply to a post.