Hi Deepthi,
Yes, You can check BAPI_ACC_INVOICE_RECEIPT_CHECK and the use the BAPI_ACC_INVOICE_RECEIPT_POST .
for more details check the test report to usage of this function module ACC_BAPI_TEST_INVOICE_RECEIPT
Hi Deepthi,
Yes, You can check BAPI_ACC_INVOICE_RECEIPT_CHECK and the use the BAPI_ACC_INVOICE_RECEIPT_POST .
for more details check the test report to usage of this function module ACC_BAPI_TEST_INVOICE_RECEIPT
Hi! The cause of the problem I reported is that the ER name fields are related to customer (via relationship) rather than the service team. We have to pick another name fields that are based on relationship type and hide away the original fields that were confusing users.
As Biju k said, you must test the same scenario in you system.
In standard, we can change the valuation class if any valid PO is not available in system.
Find the all open PO from ME2* report.
Then set deletion flag for all line item which id belong to this material, then change the valuation class for material. Then remove the deletion flag from all PO, then you can continue the further process for this material.
Note : No need to do anything for PR, you can well change the valuation class if any PR exist for material.
The above scenario is standard process.
But if you test the same in your system, you can understand it properly.
Hi Marie,
Thank you very much for your suggestion. We then change it directly in the deal.
Regards,
Oscar
Hi
You can add one more phase in your dep key with base method 0017(immediate depreciation)
Basically, assign a changeover method in dep key based on useful life. As soon as useful life is over, system will switchover to 2nd phase of depreciation key which will be based on 0017
Another option is you directly assign a dep key based on 0017 to such assets and they should depreciate in next month. I prefer 1st option
Ajay M
Hi
That's how sap has designed it.
IO are temporary measures, which accumulate costs for an event and at the end the costs are settled. Allocation feature is meant for permanent objects like CC
Ajay M
or from the LMDB web screen, choose the particular system; from the main screen, there is the Advanced button with the drop-down option "Resynchronize Technical System from SLD"
Also check your background jobs are successfully running
SAP_LMDB_LDB_* -> this should synchronise any changes/updates on the SLD to your LMDB
SAP_LMDB_NOTIFY_LDB_*
If you think there is a problem with the above process, then follow the troubleshooting guide from SAP note
1592461 - Troubleshooting LMDB Notification Consumers
Also note that some scenarios in Solution Manager uses LMDB caching so if you think there is an inconsistency, it might be worth executing the report (via se38)
rlapi_manual_namespace_resynca
choose "Clear Cache" flag
Hope this helps!
Reward if you find this useful ;-)
Hi Ludek,
I've determined the source of my problem to be that the version of Crystal Reports 2013 that I have shipped with incompatible versions of Apache Rampart and Apache Axis2. The version I see in the \SAP BusinessObjects Enterprise XI 4.0\java\lib\external\axis2 directory is 1.6.2 for Apache Axis2. The version of Rampart from the \SAP BusinessObjects Enterprise XI 4.0\java\lib\external directory is 1.3.0. These two are not compatible and we need Apache Rampart 1.6.2.
I found this other thread you are involved in Crystal Reports 2013 - SP2 availability where another user is also trying to get SP2. Can you please let me know when it is available or if you can determine which versions of Apache Rampart/Axis2 are present in the service pack. Finally I get "You don't have permission to access /a:328ro3/MyAttachments/6e331823-b955-4acf-9b6c-6d036ba923d7/ on this server." when trying to access the link to SP2 from the aforementioned thread.
Thanks!
Jeff
1753169 - PO not created from bidding engine
Please apply this note in ECC system
symptom
You create a PR in the ECC backend system and send it to the SRM bidding engine. In SRM, a PO is
created from the PR and replicated to ECC. The replication fails with the error message mepo 301:
Purchase requisition is in external sourcing.
Muthu
Hello Curterris,
Based on your screenshots, things are much clearer now.
ignore<<<The error is generated because you do not have YTIC1(its a technical name) Characteristic in your Infocube structure. I can see Characteristic Assignment do not contain YTIC1, which is correct.>>>ignore
I suggest you to pease check Grouping Condition as well - include only the valid Characteristics(verify technical name) as part of your Grouping Condition and Characteristic Assignment.
Please re-check if these all correct characteristics (YBRAND, YPRODUCT, YREGION, YSALESMAN and YTC) in your infocube. Do you have any other characteristic as part of your infocube?
Hope this will help.
Thank you
Satish Waghmare
Message was edited by: SATISH WAGHMARE
Dear Gajesh,
Haven't tested the same as there is been a logic written accordingly for a lookup and will impact flows .
Can I use these nodenames directly as selection in analysis objects? Hope it works
Hi Gobi,
The best way to delete a file from HANA server is to do it using Web IDE
As Web IDE is directly in sync with Server
Regards,
Vivek
Zakyiah Tuwaylib,
Just debug and see.
TYPE /h in the command prompt and then click SORT button.
It will help you understand how program execution takes place.
Regards.
Hi,
Is this same in both Rich client and Launch pad(info view).
- On which Bex object you have created LOV(Prompt).
- Did you check at BW/Bex end - RSRT T code and verified the list is coming properly.
What is BW version?
- Best wishes, Vijay
Hi Gajesh,
Sorry for I was not able to follow up. Gone through that document but not helped me.
Do we have any option apart from this method? I mean for a tab since there are 3 hierarchies, there are a minimum of 20 single single roles for 20 nodes. Hence we require 20 composite roles?
Hi,
V.8.82 , PL 10. Its a live db.
Regards,
Jess
Hi Sandeep,
in this case, you need to bind your standard workflow container REQ to _WI_OBJECT_ID of your task in which you are calling APPROVE method.
This will work for you
Regards,
Ibrahim Ansari