cancel
Showing results for 
Search instead for 
Did you mean: 

Handling BAPI's in EWM cases

former_member625937
Participant
0 Kudos
825

Hi Team,

I have a scenario in EWM as below as request to suggest me the same.

Steps-

1. Delivery D1 gets created via BAPI 'BAPI_GOODSMVT_CREATE', BAPI COMMIT - Movement type - 411K

2. For updating the backend table from IM to EWM , it takes sometime

3. Delivery D2 gets created via BAPI 'BAPI_GOODSMVT_CREATE', BAPI COMMIT - Movement type - 311

4. As the step 2 takes some time for the update , when step3 runs...it goes for an error stating stock unavailbility.

Is there an option to handle this case technically.

I have planned like below to follow some 2 step process...

1. Once D1 created , then D1 been updated in some custom table

2. Some reprocessing concept in selection screen, so that take D1 from custom table then do D2 document creation.

Is it fine if i go ahead with this model ?

Accepted Solutions (0)

Answers (1)

Answers (1)

sampathkumar1
Explorer
0 Kudos

Is the 311 dest is IM location?

Then you do these in EWM itself. First posting change and then adgi - move to im location.