on ‎2020 May 27 5:05 PM
Dear All,
Need your help to fix the issue of TLOGUS (Unprocessed sales) table entries delete in CAR.
When I sent IDOC (WPUUMS) from CAR to S/4 with 80 articles in single IDOC, IDOC is failed to process for only one article in S/4.
Rest of 79 articles are processed in S/4 and material document also created and decreased the stock in S/4.
But, in CAR all 80 articles are still exist in TLOGUS table. Expectation is only one article should be there in TLOGUS.
When we check inventory visibility for any of 79 articles, stock value is giving wrong values because of TLOGUS contains those 79 articles.
Business expectation is... as material document is created for 79 articles, TLOGUS should delete the entries for 79 articles. So that real time inventory visibility is correct.
In config, I have set worklist delete option as package confirmation to delete entries in TLOGUS.
Hope this is clear to all.
Please suggest how to fix the error to delete entries in TLOGUS for partial successful of IDOCs in S/4.
Thanks
Request clarification before answering.
Hi KBSR,
The standard solution for Inventory visibility in CAR works purely based on the handshake between CAR and ECC upon successful postings of Idocs in ECC.In a way CAR is depending on the idoc package confirmation from ECC to decrement the unprocessed sales records from TLOGUS table. Also this functionality works based on the idoc status in its entirety, in other words the idoc status has to be "53" and nothing else(doesn't matter whether one line item has failed or 99% of the line items failed).
I am not quite sure what is the use case for your inventory visibility solution, I can think of the following options if you are looking for intraday stocks update during the day !
1.Build a robust ECC reposting mechanism for example in case of WPUUMS idoc failing due to listing error then you can reprocess it and internally you can do the listing and reprocess it at regular intervals. This would mean your CAR stocks get updated. There may be other reasons why the idocs may fail, but it's imperative to understand the most frequent idoc errors and analyse and put together a robust solution within ECC.
2.Alternatively you can build a custom wrapper program to mimic the idoc postings in such a way that once the idocs are successfully created from CAR(status Green- data passed to port OK), you can delete it from TLOGUS(however this will be against the whole of purpose of package confirmation process within SAP Standard).Typically reprocessing of the idocs should be done by next day morning to ensure the stocks are in tact within ECC !
3.Last but not the least, raise a ticket with SAP and get their expert advise.
Hope it helps.
Thanks,
Aram.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.