1.    Introduction

1.1  Document Purpose

1.2   This is the document helps you to create custom routine for sales order for below specific requirement:

Functional description:

In case of sale order with the SD document category ‘K’ or ‘L’ or ‘H’ related to an invoice, we need to fill the fixed value date (VBKD_VALDT) with the billing reference date (VBRK_FKDAT).

For example:

Invoice 90001111, the billing date is 22.07.2013

Capture.JPG

If we create a sale order related to this invoice, we want the fixed value date equal to the billing reference date.

Capture.JPG

Capture.JPG

As per the requirement:

Sap standard routine ‘103’ triggers whenever sales order is being created with reference. Sap standard routine is configured in VOFM transaction as:

Capture.JPG

Capture.JPG

Sap standard routine ‘103’ has the functionality of copying the billing document header data and billing document line item data into the sales order header data, whenever sales order is being created using reference document.

Note: To achieve this requirement we can also enhance the SAP standard routine 103 but here they need the custom routine because it will be configured on demand basis by client whenever they need it.

About VOFM Transaction:

Capture.JPG

Transaction VOFM is a tool that was developed in R/3 to facilitate the definition of both SAP delivered as well as customer defined routines/rules used in the system during various business processes. VOFM routines are ABAP code written in Forms. VOFM provides the user with the benefit of choosing from one of the standard delivered R/3 routines or writing their own. VOFM is intended for the implementation team when configuring the system. It is not intended for the end user.

Here we have four important menus:

i)                    Copying requirements

ii)                   Data transfer

iii)                 Requirements

iv)                 Formulas

             Steps to create the custom routine:

1)     Go to transaction VOFMàData transferà Orders

Capture.JPG

2)     Provide a custom routine name

Capture.JPG

Naming Convention:

VOFM routines are organized using the Group Indicator Code. The VOFMprogram uses

the group indicator to determine the program include and subroutine names when it

dynamically creates these objects. The assignment of these names is hard coded in the program.
The valid group indicator codes are defined in data base domain GRPZE using a value range.

Go to transaction ‘VOFN’ place the cursor on class input and press ‘F1’ key.

Capture.JPG

Capture.JPG

Now double click on data element and see the domain values as:

Capture.JPG

All the fixed values are Group Indicator Code.

·         Standard SAP routine name starts from 1 to 599.

·        So all custom name starts from 600 to 999.

Now provide the custom routine name and press enter, it will ask for access key:

Capture.JPG

Once the access key provided a include program get generated with transport request as:

Capture.JPG

All include program generated from Routine has an entry in table TFRM (Form Routines for Requirements/Formulas/Data Transports) and TFRMT (FORM Routines for Reqs./Formulae/Data Transports: Texts).

1)     Double click on the custom routine 901

A modification message appears as:

Capture.JPG
Then mentioned icon in the above screen shot needs to be used for modification of the custom routine.

Now place the cursor at the end of the ENDFORM and click on the insert button to write our own code as shown below:

Capture.JPG

On clicking insert button we have the area for writing our code with *(INSERT,, *) INSERT as:

Capture.JPG
Now as per requirement above we have written following code:

Capture.JPG
Along with code for standard routine 103, the code marked in red is the additional for this specific scenario has been used.
The billing date has been copied also in VBRK value date which also gets copied into VBKD.
The standard SAP program for creating the sales order using reference document checks for all values and if found any difference between CVBRK and VBKD, it creates an additional entry for VBKD. For that reason in this scenario fixed value date is also copied into CVBRK.

Once the coding is over we need to activate the custom routine 901 and include program generated.
For confirming the same we need to check the entries in TFRM table as:

Capture.JPG

Capture.JPG
Even if any error occurs then we need to run the SAP standard program “RV80HGEN” to regenerate all VOFM routines.

Testing:

The Billing Document ’90000112’ has been used to create the Sales order :

Capture.JPG

Capture.JPG

It has the fixed value date : 22.07.2013

Now following steps has been taken to create the sales order using billing document as follows:

In VA01 transaction for a given order type(ZRD) when sales order has been created with Reference

Capture.JPG

Reference document has been taken as billing document(9000112) as mentioned above.

After clicking on the copy option, a screen will open having the information of the sales order.

Capture.JPGTransporting the custom routine to different system:

Program RV80HGEN can be used to re-generate all VOFM routines. Whenever VOFM

routines are transported this program should be executed in all target systems. It is

possible to include an automatic execution of the program in the transport request by

applying OSS note 598475.

It can be added to the transport request of the custom routine include as:

Double click on the transport request

Capture.JPG

Open it in change mode and provide input as shown below:

Capture.JPG

And press enter and save.

So when this transport is sent to target system then it gets executed automatically.

Even if it does not work then we need to run SAP standard program ‘RV80HGEN’ manually in the target system.

Activation OR Deactivation Of Custom Routine:

Sometimes while transporting the entries in table TFRM or TFRMT does not exists in target system. In this case we need to run the standard SAP program RV80HGEN first and then Standard SAP program SDINVOFM used to identify and repair missing table entries in the VOFM control tables TFRM and TFRMT.

We can also activate and deactivate our custom routine from VOFM as:

Capture.JPG

Depending upon the action the TRFM or TRFMT entries gets updated automatically as:
Capture.JPG

To report this post you need to login first.

28 Comments

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

    1. Eduardo Hinojosa

      Hi

      I can suggest you these notes

      SAP Note 156230 – Requirements: What is permitted, what is not?

      SAP Note 22808 – Transferring formulas

      SAP Note 326560 – Various problems when using VOFM functions

      SAP Note 356737 – Customer name range for VOFM routines

      SAP Note 381348 – Using user exit, customer exit, VOFM in SD

      SAP Note 327220 – VOFM function and its objects

      Regards

      Eduardo

      (0) 
  1. Eduardo Hinojosa

    Good job, but your document needs a comment. The range for VOFM according Note 327220 – VOFM function and its objects in “2.2 Namespaces” is for FOFU (this case from 900 to 999), in detail:

    Subsequent functions from 900 to 999 (FOFU this case)

    Group key routines from 50 to 99

    Data transfer routines f. texts from 50 to 99

    all other indicators from 600 to 999

    Regards

    Eduardo

    (0) 
  2. madhu kumar

    Hello Mohammed Khurshed,

    Your Explanation is very clear and easily understandable and Document is very helpful.

    Continue the good work…..

    Thanks and Best Regards,

    Madhukumar 

    (0) 
  3. Anbuselvan SD

    Hi Mohammed,

    Thank you for the well illustrated document. It would be helpful for newbie’s like myself. But I am  unable to understand the business need to fill the fixed value date (VBKD_VALDT) with the billing reference date (VBRK_FKDAT).

    In what scenario, the business would like to have this kind of requirement.. since we have a field called service rendered date..

    sap sd 1.JPG

    (0) 
  4. Christian Tapia Sabogal

    Thanks for this post!!

    Just an aclaration, when adding the program RV80HGEN to the Transport Request, it should be of type XPRA, and not PROG. As the description says: “Program executed after transport”

    (0) 

Leave a Reply