Hey guys,
we have a Problem in creating automatic packaging material item in ERP after GI posting in EWM.
We activated the packaging item Generation in EWM via customizing. HUs are created in EWM and respective delivery item is being created in EWM (item number in EWM is simply increasing highes item number + 10).
Now upon GI posting we send update to ERP based on Standard PPF. On ERP side a new item is being created simply by counting up existing highest item number +10. This causes Problems in EDI communication with our partners .
What I know from ERP usage without EWM the Standard will always add the packaging mateiral items with item number 900001 ff.
Does anybody have any idea how to Control this item numbering? I want to get my packaging material items with 900001 ff. numbering as if we were use to it without EWM delivery processing.
Thanks a lot for any Input!
Hi Hendrik,
Please check the BADI/Enhacement Spot:/SCWM/EX_ERP_MAPOUT_OD_CHANGE/SCWM/ES_ERP_MAPOUT
This spot will help to change mapping data from EWM to ERP in Inbound/Outbound.
Kind Regards,
Ajit
...so you would suggest to Change the item numbering here? This will be rather complex as we Need to consider other items which might be created based on the internal 9***** range (e.g. Batch split items).
So you agree that there is no option to have Standard behave in the same way as it we were using WM only!? (so Standard will not consider the internal 9***** range as the packaging material item is provided externally (here from EWM))
Hi Hendrik,
Automatic packaging material item is created with reference documents i.e, below ref doc category, ref Doc,Ref Item no ( Which is the item no for ERP/ECC Item and same item number will supply to ERP/ECC for Pack item )
ERO ( ERP Original Document )
ERP ( ERP Document )
control of Ref Item no: As per Standard , this no increment from below SAP Config
SPRO->SCM Extended Warehouse Management->Extended Warehouse Management->Interfaces->ERP Integration->Delivery Processing->Control Message Processing Dependent on Recipient
Doc Type ERP ItemIncr( 10 )
This is the standard increment 10, but you can change ,Impact as per the document type.
EWM always use to determine next erp-itemno using below logic same as ERP.
* batch: 9000xx
* item: 0000xx
Please check class and method for reference
Method: GET_LAST_ERP_ITEMNO_PRD
Class: /SCWM/CL_DET
Note: According to Standard,
1> If Packaging Item or new item add to delivery is batch managed, Item no will follow the series 9XXXXX.
2> If Packaging Item or new item add to delivery is not batch managed, Item no will not follow 9XXXXX, but It will add as per the above settings. Suppose you maintain 200000 in the above settings and delivery have 2 items 10,20, then new item will Max + config value.200000+20= 200020 Ref Item no.
Hope I answer your queries.
Please let us know if you have further queries.
Kind Regards,
Ajit
Hi Ajit,
this confirms what I mentioned above.
2> If Packaging Item or new item add to delivery is not batch managed, Item no will not follow 9XXXXX, but It will add as per the above settings. Suppose you maintain 200000 in the above settings and delivery have 2 items 10,20, then new item will Max + config value.200000+20= 200020 Ref Item no.
This will always be true for packaging material (packaging material will never be managed - at least I've never seen this) so we will never get a number from 9000** range. So there is a deviation compared to the behaviour with LES/WM only as here we would always get a number from 9000** range for packaging materials which are added based on the HUs created during packing.
Regards,
Hendrik
Hi Hendrik,
I was aware of your requirement that is why I mentioned the standard EWM behavior and could not find any standard config for your requirement as per my knowledge.Sorry, as per my understanding, It seems bit difficult without SAP Support.
Did you raise OSS message for the same ?
Kind Regards,
Ajit
...no as I assume a 'works as designed' feedback ;-).
We implemented a custom logic in the Interface to the Client in order to reach the objective of our requirement.