Skip to Content
0
Former Member
Oct 15, 2012 at 10:04 AM

XLIKP Common Part Problem Using WS_DELIVERY_UPDATE_2

156 Views

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