XLIKP Common Part Problem Using WS_DELIVERY_UPDATE_2

[Former Member]

Hi all,

I have a strange behaviour with XLIKP which is defined as common part within SAPLV50S and SAPMV50A.

If I call function WS_DELIVERY_UPDATE_2 from my report, everything is normal and XLIKP gets appended in form fill_deli_header (SHP_CORE_FILL_COMMON_PARTFDH) for both, SAPLV50S and SAPMV50A.

But if a Batch-Input (VL02N) was running short before the Call of WS_DELIVERY_UPDATE_2, XLIKP only gets filled for SAPVv50A. XLIKP of SAPLV50S is available, but gets not filled (so it's not common part!)

Any clues? How can (SAPLV50S)XLIKP be assigned but not being common part ??? The Call Transaction VL02N must do sth. which confuses the common part.

I played around with commit work and initialisations and call with destination - no luck

Thanks & Cheers

carsten

[Former Member]

Hi,

Try to Check this BADi  LE_SHP_DELIVERY_PROC.

Now you can play anything within this BADI.

[Former Member]

A BADI does not help here since it cannot replace (but enhance) the call of WS_DELIVERY_UPDATE_2 !!!

Any other clues?

[Former Member]

Hi,

Have you found any solution to this problem?

I am facing the same issue with WS_DELIVERY_UPDATE_2 you are describing, but cannot see any good solutions witout enhancing the standard code.

Best regards,

Bjørn A. Flatby

[Former Member]

Hii Bjørn,

the common part mess was caused by an external call (lieferung_sperren(sapmv50a)) within my report before calling function WS_DELIVERY_UPDATE_2.

That external perform was binding the Common Part of sapmv50a to my ALV function group instead of sapmv50S

I've copied the coding of lieferung_sperren(sapmv50a) to my report and everything is fine now.

Cheers

carsten