Delivery Block at PGI level based on GI date and Month end date

[Former Member]

Business need a check on delivery processing based on the Planned GI date, Month end date and transit period. This transit period is a custom field and dependent on customer. Also it is not maintained anywhere in system. Business store it in some excel format.

The logic needed is: For any given month, the delivery order MUST be goods issued in the same month, i.e. once the order is delivered, the Post goods issue should ONLY be allowed if and only if , the PLANNED GI date ( as maintained in delivery ) + transit time ( at customer level ), falls within the month end date. If not, a block should be applied at PGI and only authorized personnel should be able to release that block.

Also, there will be no check at invoicing VF01 level. Once the PGI blocked is removed, there will be no check on invoicing. The month end date may vary month to month and need to in combination of Sales Org / Plant as mentioned

In addition, the business need an exception report where the information of releasing the block should appear for release date, user id of the responsible person, time sales order no etc. and it should be downloadable.

We can have a custom table to maintain the month end day in given combination.

But I need your expert inputs as-

1- Can we add this transit period in at customer master data as it is dependent on customer and there are huge no of customers for the sales unit? If not, then how to maintain it; may be a z table?

2- Based on this logic, what should the code/logic to be written for block at PGI.

3- How to control the authority check for removing the block.

4- The source fields for exception report.

Pls revert accordingly.

Many thanks in advance.

[jignesh_mehta3 · Accepted solution]

Hello,

Please refere the answers to your questions:

1- Can we add this transit period in at customer master data as it is dependent on customer and there are huge no of customers for the sales unit? If not, then how to maintain it; may be a z table?

You can either use some un-used Feild in Customer Master or maintain a Z-Table. I believe maintaining a Z-Table would be easy as you have huge number of Customers. You can also write a dmall program to Pick the Customer-wise transit dates from a excel file & store in Z-Table.

2- Based on this logic, what should the code/logic to be written for block at PGI.

You have explained the requirement well in your thread, you need to explain the same to your ABAPer & Basis person & they would do the needful.

3- How to control the authority check for removing the block.

Basis person would create & assign a Z-Authorization object which the ABAPer would use in his program.

4- The source fields for exception report.

Once you do the above development, your ABAPer will easily pick the required feild in Report as he has already used all the feilds somewhere in his development.

Hope this helps,

Thanks,

Jignesh Mehta