cancel
Showing results for 
Search instead for 
Did you mean: 

Outbound Delivery quantity becomes Zero

Former Member
0 Kudos

Dear All,

I am facing a peculiar issue with Outbound Delivery.

A Sales order with a Material with 1 quantity and Outbound Delivery created for the same by a background ground.

After some time, another Outbound Delivery created for the same Sales order. After 5 seconds, quantity in the first Outdound Delivery made to Zero by a background job. Picking status changed to "Not Relevant for Picking" for the line item in the first Outbound Delivery.

We are unable to find out the details from the Background job since it is not generating Spools.

There is no change in Item category and Delivery type configuration in the recent days.

I suspect it may be an APO issue. But not 100% sure.

I request you to share your knowledge if you came across similar situation.

Regards,

Raja Durai

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

As correctly mentioned by Shiva, details are required.

But to add, I faced a similar kind of situation sometime back and for us the culprit was the background job itself.

In the Background job, while the data for the first delivery was being processed, the same SO was processed again and another delivery was created (as the VBFA flow etc. were not completed by then). so It actually went in some sort of a spiral, where the same SO was processed multiple times and the number range of delivery was consumed without any use.

Check the variants and try and modify the variants (if Std prog is used) to ensure the one SO is processed once only.

Former Member
0 Kudos

Hi All,

Thanks for your reply.

Due to some problem with the existing username I was unable to post the comments.

We discussed with APO team, and found it is not APO issue.

We are using RVV50R10C program to create Outbound Delivery.

Variants are created in the T code "VL10BATCH". In the Variant, "Only Open Deliveries" option is not marked.

Could someone explain the impact of the this field if not marked.

Also kindly explain what are all the things to be checked in the background job program and its variant.

Regards,

Raja Durai

Former Member
0 Kudos

Only Open Deliveries" option is not marked.

- this is what I said was the main culprit (similar case as explained earlier).

Since you are not checking " ONLY OPEN DELIVERIES" so the system will start processing all deliveries irrelevant of their GI Status. and hence creating problems.

Former Member
0 Kudos

Hi Sachin,

Thanks for the response.

But issue was different. We identified that.

It was because of an incoming IDoc. SHPCON IDoc received with SPLIT qualifier. That is making the quantity zero in the Original Delivery and creating new delivery.

Regards,

Raja Durai

Shiva_Ram
Active Contributor
0 Kudos

Without clear details, it is hard to suggest solutions by the members.

After 5 seconds, quantity in the first Outdound Delivery made to Zero by a background job.

What does this mean? Do you mean another background job other than delivery creation is running in the system?

Why don't you post the screen shots of the back ground jobs?

Also you have mentioned that you suspect APO issue. What is the basis for it? If you suspect, then did you discuss with the APO specialist? What analysis is made on APO side?

Without proper analysis on your part and description in the question posted, members can't provide any good solution. All you will see is endless questions on this thread.

Regards,

former_member184065
Active Contributor
0 Kudos

Dear,

A Sales order with a Material with 1 quantity and Outbound Delivery created for the same by a background ground.

How you have created Two Deliveries based on Sales Order with only One quantity ?

You have created Sales Order with 1 Quantity and created Delivery with 1 Quantity .

Again ,you went to create OBD based on same Sales Order .Now ,coming to the point is where is the Quantity to conform for First OBD ?

I request you to check both OBD's and in one of the Delivery should have that Quantity 1 .

Thanks,

Naren