Skip to Content
Author's profile photo Sagar Gaikwad

Return PO delivery creation error for AFS materials

BACKGROUND

User is trying to return AFS material to vendor using return PO with delivery. PO is created and outbound delivery is created using VL10B then that delivery is deleted and when user is trying to create another delivery for same PO, system was showing ABAP dump. Material used in this case is AFS – Batch Managed material.

BUSINESS PROCESS

AFS materials are returned to vendor using return PO with delivery. These materials are batch managed. Since these materials are AFS materials, so different grids with different quantities, different batches are maintained in return PO (Depending on whatever quantity to be returned). Outbound delivery is created through VL10B and then PGI.

CHALLENGES

When outbound delivery is created against AFS material return PO then AFS table J_3ABDBS is getting updated with line item. But if we delete that delivery then J_3ABDBS not getting updated correctly. This is causing ABAP dump while creating delivery again using VL10B.

After creating delivery; table J_3ABDBS gets updated as below

/wp-content/uploads/2015/09/1_789892.jpg

When delivery is deleted table J_3ABDBS was not getting updated correctly. Entries were remaining in table even after deletion. This was causing problem.

/wp-content/uploads/2015/09/2_789893.jpg

This incorrect table entries causing ABAP dump while creating new delivery for same return PO. Same ABAP dump is getting displayed if we try to check Delivery schedule where different grid values are maintained in one line item of PO.

/wp-content/uploads/2015/09/3_789894.jpg

New delivery can be created using transaction VL10D but system will not distribute the quantity correctly and also PGI can’t be posted for that delivery.

  /wp-content/uploads/2015/09/4_789895.jpg

PGI Error message – 8J-182

/wp-content/uploads/2015/09/5_789899.jpg

SOLUTION

1.    Maintain Automatic Deallocation configuration for AFS specific delivery type. System will deallocate schedule lines of return PO after delivery deletion.

/wp-content/uploads/2015/09/6_789900.jpg

2.    Install SAP note 2206134Allocations not completely deleted when deleting return delivery in VL02N. This will correct the problem of J_3ABDBS table update.

Before delivery deletion

/wp-content/uploads/2015/09/7_789901.jpg

After delivery deletion

/wp-content/uploads/2015/09/8_789902.jpg

3.    Install SAP note 2173710 – VL10B: Incorrect delivered quantity displayed for return PO

NOTE

This AFS program error was reported to SAP (OSS Message – 261344/2015 and 573255/2015) by us and against which SAP has created this new note 2206134 – Allocations not completely deleted when deleting return delivery in VL02N (Released – 19 Aug 2015) and 2173710 – VL10B: Incorrect delivered quantity displayed for return PO.

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo RAMESH SRINIVASAN
      RAMESH SRINIVASAN

      Hi

      what was the reactive measures taken for clearing the J_3ABDBS entries

      Thanks & Regards

      Author's profile photo Sagar Gaikwad
      Sagar Gaikwad
      Blog Post Author

      SAP Notes 2206134 and 2173710 are useful to clear the incorrect entries from J_3ABDBS. These are mainly to remove inconsistencies between IM and AFS.

      Author's profile photo RAMESH SRINIVASAN
      RAMESH SRINIVASAN

      Hi Sagar

      Thanks for the response, even I am also facing the similar issue

      I tried implementing the SAP Notes 2206134 and 2173710 , but the incorrect entries which already exist in the table J_3ABDBS still not cleared , whether this note will avoid the inconsistency in future , or it will clear the incorrect entries which already exist in the table

       

      Best Regards

      Ramesh