Hi Yajepenati,
Have you tried to add a member into the dimension from web admin? then process the dimension again.
Andy
Hi Yajepenati,
Have you tried to add a member into the dimension from web admin? then process the dimension again.
Andy
Hello Smriti,
you have several options to reach your goal. For example you can create a view and expose the view via the OData service.
Another option would be to expose both tables in the OData service with an association + navigation property between the two entities. By using the $expand option you can get the properties of both entities at one time (e.g. .../FirstEntitySet(A='Value1')?$expand=toSecondEntity).
Best Regards,
Florian
Please share what you did so that others get the help.
Regards,
Gaurav
Hi Gabriele,
I will need access to the SAP Cloud Identity tenant.
I couldn't find any information as yet on how I can get that.
Can you please help.
Regards,
Subhasish
Hi Bhaskar,
Yes PR/PO is created with proper Account Assignment Category using proper WBS.
Regards,
Omkar
Hi All,
We have a following scenario:
While creating a sales order in SAP CRM we are using ATP check to confirm the stock for the material. However if the stock is not available in customer default plant and is being bought from other plant there is a plant substitution which happens as a part of SAP standard and you get one main line item and one sub item.
However when there is a delivery block on the line item what should be the standard SAP behaviour? I assume system should delete the sub line item and flip the item category of main line item to its original item category like TAN.
However our current behaviour is that system retains both line items and does not delete the sub line item. Please suggest if my assumption on standard behavior is correct.
Also please suggest what could be the possible solution for this issue.
Regards
Yogesh Kathe
Please refer to this Blog on Kerberos SSO.
Regards
vikas
We have developed Analytical views, Analytical Privilege and Analytic Procedure.
The Analytic Privilege is connected an Analytic View and the data restriction is via the Analytic Procedure.
The filter for data restriction is obtained from the OLTP schema as String. and that is populated into the VAR_FILTER object.
VAR_TABLE = APPLY_FILTER("_SYS_BIC"."MY_SCHEMA.MY_PACKAGE/MY_ANALYTIC_VIEW", :VAR_FILTER); |
The above line of code is in the Analytic procedure.
We have created a restricted user and granted him the following roles/privileges
GRANT SELECT ON SCHEMA _SYS_BI TO RESTRICTED_USER;
GRANT EXECUTE ON SCHEMA _SYS_BI TO RESTRICTED_USER;
GRANT SELECT ON SCHEMA _SYS_BIC TO RESTRICTED_USER;
GRANT EXECUTE ON SCHEMA _SYS_BIC TO RESTRICTED_USER;
GRANT EXECUTE ON REPOSITORY_REST TO RESTRICTED_USER;
GRANT RESTRICTED_USER_ODBC_ACCESS TO RESTRICTED_USER;
GRANT RESTRICTED_USER_JDBC_ACCESS TO RESTRICTED_USER;
GRANT SELECT and EXECUTE on the data schema is also provided to the user.
Access to the Analytic Privilege is also provided to the user.
When we execute the APPLY_FILTER command with the view as the object to filter as a restricted user results in the following error.
SAP DBTech JDBC: [258]: insufficient privilege: [2950] user is not authorized
If we replace the view to a table in the APPLY FILTER condition, it does not throw any error and works fine.
If we grant additional privilege such as MODELLING or CONTENT_ADMIN, then the filtering does not happen, and all records are shown.
Do we need to give any special privilege for a restricted user to execute the following command in a Analytic Procedure ?
Hello Silvia,
F110 clears only vendor invoice and keeping payment line items open in outgoing bank account GL.
In case of alternative payee also the invoice should be cleared.
Can you elaborate about your query?
Best Regards,
Chirag Panchal
Hi Babu,
Check the GL account assignment for cross company in OBYA.
Regards,
Mukthar
Hi Clark,
Could you resolve the above issue since DMS integration with TM is not available in any of the versions.
Hello Luis,
for that I found for myself also no real solution. The insert statement created by the XSDS API does not uses only the fields provided with a value in the field list. So the insert statement fails with the error, cause no value is provided for the "not null" fields.
As a workaround I specified the initial values for the required fields when the $importEntity method is called. Via the $init property value can be specified for new created instances. It is not really nice, because the default values are defined at two places, but to my knowledge up to now the only way to reach the goal.
For your example something like that:
var user = XSDS.$importEntity(<namespace>,<user entity name>, { role: { $init: 2 }, nb_login: { $init: 0 }, status: { $init: 0 } } );
Best Regards,
Florian
Hello Vishal,
Are you seeing any error logs in the transaction /IWFND/ERROR_LOGS on the front end server? Also do you see any missing authorizations in both front end and back end servers?
Regards,
Saurabh
Hi,
Actually it really depends on where you are inclined to..You can also be good in BI even if you like to work with databases..It really depends on whether you will enjoy the work of BI guys since you will still undergo training whatever module you will grab..
Regards,
Loed
And when you do this * manually in the batch number field then the next step is still manually, then the user has to select the batch of his choice in case there are multiple even to enter the quantity how much he wants from which batch.
please see Q&A 5 in OSS note 520813 - FAQ: BAPIs for goods movements
and see an example in
Thank you all. We created a custom auth object and the developer included the auth check to the code and we got the desired result.
Rgds,
PD
Hi Mark ,
At PI we have field data type as HexBinary which is converted as data type ""RAWSTRING' in proxy. We are passing data from xstring data type to ""RAWSTRING" field .
I dont see any issue here . what you suggest ?
But in SXMB_MONI field showing non Hex data in the field .
Regards ,
PD .
You can above BOM in standard production order. In planned stage, you can select either one raw material based on in-stock field from row level.