Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SDPICK IDoc stays in status 64 when partial delivery

Former Member
0 Kudos

Hello,

I'm receiving SDPICK IDocs from an external warehouse management system to update the outbound deliveries in SAP, and post the goods issues there. This works fine when all quantities can be sent to the customer.

Problem occurs when for example customer requested 56 materials, and we have only 20. In that case a partial delivery should occur. So the E1VPDLH-KOMUE field is set to X so that the picked quantity is copied into the delivery quantity. Unfortunately, the IDocs for which the delivery quantity is not equal to the picked quantity stay in status 64. If I process them manually (with transaction BD87), a popup screen appears with the following message (attached): Do you want the quantity change to be documented ? I can answer the question (YES or NO) and then the IDoc is set to status 53 and the delivery updated (delivery quantity receives the picked quantity). Unfortunately, when the IDoc is processed automatically, there is nobody to answer that question, and that's why it stays in status 64.

Do somebody know how this message can be disabled ? Or answered automatically ?

Many thanks in advance for your hints !

Kind regards,

Mathieu

5 REPLIES 5

anjaneya_bhardwaj2
Contributor
0 Kudos

The error is based on the Quantity difference profile ..I think best would be to check with the functional to alllow the overwright to happen without documenting the change that is storing the history .Not sure but may be below link can give you some insight into it ..

http://help.sap.com/saphelp_di471/helpdata/en/90/ef36565bc2dd4aa2d22adb28430f74/content.htm

On the Technical side . This  message not coming during IDoc creation but when You are trying to post the Idoc to appllication as this is standard(best way if you can avoid this message via config) .

I would suggest create an Inbound FM to process the Idoc which will use BAPI to do the PGI (Partial delivery ) and quantity update .Have a mechanism to track the Status.As even the BAPI will return the message.

Another Unconventional way would be to have an Enhancement point to overright the message when the User is Background (This enhancement will have to be done in your VL02n) and will not allow the Pop up to come if the backgroun processing is happening ..

I believe you have WABUC field in the incoming segment already set ..

Thanks,

Anjaneya ,

former_member215575
Active Participant
0 Kudos

Mathieu Sutter wrote:

If I process them manually (with transaction BD87), a popup screen appears with the following message (attached): Do you want the quantity change to be documented ? I can answer the question (YES or NO) and then the IDoc is set to status 53 and the delivery updated (delivery quantity receives the picked quantity).

Hi Mathieu,

It seems that there is an exit/enhancement written in BD87 to popup the confirmation message as SAP standard do not display any popups.

As per my understanding it should result in short dump as pop-up's are not allowed in background.Please check on ST22 if you have got an runtime error 'DYNPRO_SEND_IN_BACKGROUND' with exception 'CX_SY_SEND_DYNPRO_NO_RECEIVER'.

You can check in ST22 where is it resulting in dump.

Regards,

SG.

0 Kudos

There are dumps in ST22 with error 'DYNPRO_SEND_IN_BACKGROUND' even if I can't find the exception that you mentioned. The calling system also gots an error from RFC like : Sat Apr  7 16:40:19 2012] sendsapdata: Message Screen output without connection to user

But at that time I have no solution to avoid that. We'll try to explore the Quantity difference profile...

0 Kudos

Hi Mathieu,

If dumps are seen(cause of IDoc status 64), figure out from where it is triggering from and avoid that exit/enhancement or atleast other than excluding exit/enhancement try to avoid pop-up in background(sy-batch = 'X' something like that if sy-batch is being captured correctly). 

Hope this will solve the issue.

Regards,

SG.

Former Member
0 Kudos

Thanks Sravan, we indeed finally found an OSS note 460134 that does the same as you suggested !

Kind regards,

Mathieu