VF04 is the transaction used to display the billing due list. It displays only those deliveries which are posted or whose PGI is complete. If we need deliveries which are not posted also to appear in the output list, we have explore enhancement user exits. This document explains how we can achieve this new functionality.

Procedure:

In order to find the deliveries which are not PGI ed we can use the transaction VL06o.

/wp-content/uploads/2014/10/1_563391.png

By clicking on push button  “For Good issue” we can let the list of deliveries which are not yet posted in the system.

/wp-content/uploads/2014/10/2_563392.png

Execute this report after giving relevant criteria for your search.

The output would look as below:

/wp-content/uploads/2014/10/3_563438.png

Now we can check in VL03N,for the document flow of this outbound delivery.

/wp-content/uploads/2014/10/4_563439.png

It is clear from the above document flow that, PGI has not been done.

Now, we can execute VF04 for this delivery: Result: No entry found

/wp-content/uploads/2014/10/5_563440.png

Steps to achieve the intended functionality to display the above delivery in VF04 output, for which goods issue is not done.

1.  1. Check and note down the program name for VF04 tcode : SAPLV60P

/wp-content/uploads/2014/10/6_563441.png

1.  2. Using this package we can search the list of userexits for tcode VF04 either in SMOD or SE80.

3. Go to SE80 and search for relevant exit:

/wp-content/uploads/2014/10/7_563442.png

4. Following list appears. We are interested in the billing list for deliveries:

/wp-content/uploads/2014/10/8_563443.png

We have to keep in mind that we are looking for something where we can check and use the billing status of the delivery.

/wp-content/uploads/2014/10/9_563444.png

/wp-content/uploads/2014/10/10_563445.png

Also, we need to debug VF04 to some extent to know from which database table does the report display data.

Program SDBILLDL is being called at F8

The relevant code part of the standard program is shown below:

/wp-content/uploads/2014/10/11_563446.png

/wp-content/uploads/2014/10/12_563447.png

/wp-content/uploads/2014/10/13_563448.png

/wp-content/uploads/2014/10/14_563449.png

So we are aware that VKDFS table has been used to fetch data that would be displayed in VF04 output.

5. Further exploring the exit:

/wp-content/uploads/2014/10/15_563450.png

EXIT_SAPLV05I_002 is related to our scenario. However, this exit would not be called during VF04 for delivery.

As I have pointed out earliar, VKDFS table would be updated and this is called during delivery updation.

I have created a new delivery for this purpose.

/wp-content/uploads/2014/10/16_563451.png

Let me place a break point within the exit which we have found.

  /wp-content/uploads/2014/10/17_563452.png

   /wp-content/uploads/2014/10/18_563453.png

Now we will do the picking for the delivery :

Go to picking tab and enter the picking quantity and save the delivery.

The customer exit would get called.

/wp-content/uploads/2014/10/19_563454.png

The picking is complete!

Hence, we have found the correct exit.

1. 6.  The coding would depend on project requirements but for the above functionality to work we need to make sure table VKDFS gets updated.

IMPORTANT: Currently VKDFS would not have an entry since PGI is not done for the delivery.

During picking we would make a forceful entry in VKDFS for our delivery and hence, that would later appear in VF04 output.

/wp-content/uploads/2014/10/20_563455.png

FKSTK = Billing status

KOSTK = Overall picking / putaway status

Both have same domain values.

1.  7.  Lets now do the picking for another delivery to check how VKDFS gets updated.

     /wp-content/uploads/2014/10/21_563456.png

     Make picked qty as 1 and save delivery. The debugger will be called.

     /wp-content/uploads/2014/10/1_563391.png

     8. The code is we have written in the exit would get executed now.

     /wp-content/uploads/2014/10/2_563392.png

     /wp-content/uploads/2014/10/3_563438.png

        The importing field from the above customer function exit determines whether it should populate an dupdate VKDFS or not.

     /wp-content/uploads/2014/10/4_563439.png

      9. Now VKDFS updation in standard code.

     /wp-content/uploads/2014/10/1_563391.png

     /wp-content/uploads/2014/10/2_563392.png

       10 . Lastly you now check the delivery to be present in VKDFS table.

    /wp-content/uploads/2014/10/1_563391.png

       11.  Now our functionality has been coded and tested. Lets us finally check VF04. You can find that this delivery, even if not PGI ed ,  it appears in billing due list output.

    /wp-content/uploads/2014/10/2_563392.png

 

 

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Rahul Nayak

    Hi Sapna,

    Nice document. Agree that enhancing VF04 will fulfill the requirement to display deliveries against which PGI is not done. Usually it is not recommended to enhance/modify standard SAP reports. It is always better to develop our own customized reports to suit the requirement. To avoid developing a report from scratch, we can copy the standard report and then do the modifications required and assign a ztcode to it.

    (0) 
    1. Sapna Rao Post author

      Hi Rahul,

      Thanks for your valuable feedback.

      The requirement was very specific to the client who did not want to use any Z copy of standard report. They rather wanted some logic specific only to a couple of sales organizations. 

      However, we have a user exit in place for the above functionality.

      I have gone through SAP note 356061 – Incorrect index compilation caused by own checks

      before I could arrive at above solution.

      Regards,

      Sapna

      (0) 

Leave a Reply