BDC on collective processing VL10B

[Former Member]

Hi,

I had posted a previous requiremnet wherin we were searching userexits for VL10B, posting deliveries for PO, whern we needed to chaneg the storage location on delivery created to a different one from the config. Is it possible to capture teh delivery from the collective logs and do a VL02n on it? If so, where do we get these logs from, it is stored under a group name and userid. Any idea how to pick this up? Thanks.

[Former Member]

Hi,

I had posted a previous requiremnet wherin we were searching userexits for VL10B, posting deliveries for PO, whern we needed to chaneg the storage location on delivery created to a different one from the config. Is it possible to capture teh delivery from the collective logs and do a VL02n on it? If so, where do we get these logs from, it is stored under a group name and userid. Any idea how to pick this up? Thanks.

[Former Member]

Hi,

You can view the Collective processing log using the transaction code V_SA. The tables that store the log is

VBSK,VBFS and VBSS.

You might get some idea if you look at the program SDSAMPRO used for the tcode V_SA.

Thanks

Giridhar

[Former Member]

Hi Shobana,

Try using copy routines. Otherwise you can use Userexit MV50AFZ1/USEREXIT_SAVE_DOCUMENT_PREPARE to get the storage location of the reference document using lips-vgbel and lips-vgpos and modify the same in the current delivery.

Thanks,

Rajesh.

[Former Member]

Hi Rajesh,

This calls the delivery processing in backgraound and uses the V50R FUGR , SHP_VL10_DELIVERT_CREATE and our userexits on SAPMV50A are not triggered here, as this is a delivery creation for Purchase order. Have u worked on this aspect?

[Former Member]

Hi Nayudu,

Can you tell me what is the best way to identify the deliveries created by a collective processing after each run? How do we capture the Group id? Is there any exit routines where we can code these?

[Former Member]

We had similar requirement and using VL10D to create deliveries for PO's. We used the SAPMV50A/USEREXIT_SAVE_DOCUMENT_PREPARE user-exit to determine the carrier partner for the deliveries and it worked.

Put an endless loop in this exit. Run transaction VL10B, debug the back ground job and check if it stops here.

Message was edited by: Rajesh Mandalapu

[Former Member]

HI Nayudu, rajesh.

Got this problem solved by identifying a BADi in shipping, which triggers the same SAVE_DOCU_PREPARE thru classes.VL10B stops in this BADI.

Thanks for all ur help.

Problem is solved.