2013 Jun 16 12:40 PM
Hi,
I do have a problem with a lot of IDOC's which seems to get a wrong numbering, but I don't have any idea why.
The background for that problem is our replenishment flow, when users create there PO's the IDOC get transfered and everything goes fine.
At the state where the deliveries are created a second IDOC should create the inbound, but then the problem appears as the IDOC get status 51 after I did a follow up and correction in BD87 I found out that the POSNR and POSEXNR is wrong. As long as the PO keeps only the item 10 the POSEX POSNR in the IDOC is calculated to 1,2,3,4 and so on, where the correct combination is 1,1,1,1. Maybe it's important to mention that we are running SAP AFS.
Maybe anybody in the community does have a hint for me?
best regards
Alfons
Hi,
I do have a problem with a lot of IDOC's which seems to get a wrong numbering, but I don't have any idea why.
The background for that problem is our replenishment flow, when users create there PO's the IDOC get transfered and everything goes fine.
At the state where the deliveries are created a second IDOC should create the inbound, but then the problem appears as the IDOC get status 51 after I did a follow up and correction in BD87 I found out that the POSNR and POSEXNR is wrong. As long as the PO keeps only the item 10 the POSEX POSNR in the IDOC is calculated to 1,2,3,4 and so on, where the correct combination is 1,1,1,1. Maybe it's important to mention that we are running SAP AFS.
Maybe anybody in the community does have a hint for me?
best regards
Alfons
2013 Jul 08 12:12 PM
Hi Alfons,
the number of an IDoc is actually not serialized. This is because the Idoc number range is buffered.
So if you have more than one application server, you will see the number jumps.
Please see note 752194 which has more information regarding the issue.
Hope it helps.
Kelly
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |