Passing custom field values to the accounting document during GR/Invoice posting.

Step 1: Create an FM with parameters and table structures similar to the example below.


Step 2: Implement the code as shown below and active.

DATA: l_f_ebeln TYPE ebeln.
  READ TABLE t_accit INTO DATA(lr_accit) INDEX 1.
  IF sy-subrc = 0.
    l_f_ebeln = lr_accit-ebeln.
  ENDIF.
  IF l_f_ebeln IS NOT INITIAL.
    SELECT ebeln,ebelp,zz_prd_code,zz_veh_type
      FROM ekpo INTO TABLE
      @DATA(lt_ekpo)
      WHERE ebeln EQ @l_f_ebeln.
  ENDIF.
  IF lt_ekpo IS NOT INITIAL.
    LOOP AT t_accit INTO DATA(lr_accit1) WHERE koart = 'S'.
      READ TABLE lt_ekpo INTO DATA(lr_ekpo) WITH KEY ebelp = lr_accit1-ebelp.
      IF sy-subrc = 0.
        lr_accit1-xref1 = 'XREF1_TEST'.
        lr_accit1-xref2 = 'XREF2_TEST'.
        lr_accit1-xref3 = 'XREF3_TEST'.
        MODIFY t_accit FROM lr_accit1 TRANSPORTING xref1 xref2 xref3 .
      ENDIF.
    ENDLOOP.
  ENDIF.


Step 3: First, we need to identify the relevant FM. Once we find it, we can enhance it and add our custom logic there.

            FM: FMRE_FI_BELEG_CHECK

  1. Go to SE37, enter the FM name FMRE_FI_BELEG_CHECK, and click Display.
  2. Go to Edit → Enhancement Operations → Show Implicit Enhancement Options.
  3. Place the cursor on the Implicit Enhancement option and click the Enhance button.
  4. Right-click → Enhancement Operation → Create Implementation → Code.
  5. Click Create Implementation, then provide the Implementation Name and Short Text.
  6. Click Pattern and enter the FM name.
  7. Please find the screenshot below for reference.
  8. Check and activate.

Testing: I am posting GR

  1. Create a new PO or use an existing PO.
  2. Execute T-code MIGO, enter the PO number, and select Movement Type 101.
  3. Fill in all the required details and select the Item OK checkbox.
  4. Click Check to validate the document, then click Post to post the Goods Receipt.
  5. Goto PO screen and select purchase history tab. Click on GR.
  6. Goto doc info and click on fi documents. double click on account on accounting document.

******************************Thank you*******************************

Comments

Post a Comment

Popular posts from this blog

Custom entity/Action dialog in RAP using Unmanaged scenario

Image
A custom action is like a button (e.g., Approve , Submit ) shown in the Fiori app. A dialog is a popup where the user can enter some input before performing the action.                    Refer:-  Determination + Side effects(On Modify) in RAP Unmanaged                    Refer:-  Determination + Side effects (On Save) in RAP Unmanaged Step 1:   Create behavior definition for abstract entity.          * Right click on Core data service - New - data definition.          * Give name and description.          * Click on Next.          * Select Abstract entity with parameters and click on finish. @EndUserText.label: 'Abstart entity for status field' @Metadata.allowExtensions: true define abstract entity ZA_AB_STUH_13 //with parameters parameter_name : paramet...
Read more

New syntax for append- VALUE (new syntax 7.4+) in ABAP

Image
* We use APPEND statement to insert the records at the last of the internal table. * In SAP ABAP new syntax, we can use VALUE expression instead of APPEND statement. * Value expression is a powerful mechanism to declare as well as initialize the internal tables. * It is a powerful utility where we can achieve the result with minimal coding. * Value expression is of 2 types.      -  Define the type before using it with VALUE keyword. The type defined is structure type  or table type.      -  Using # character for type and use it with VALUE keyword. Report REPORT  zab_rp_append_value . TYPES :  BEGIN  OF  ls_stu ,          st_id ( 10 )    TYPE  n ,          st_name ( 15 )  TYPE  c ,         END  OF  ls_stu . DATA :  lt_stu  TYPE  TABLE...
Read more

Read statement new syntax in ABAP. (7.4+).

Image
*  Before ABAP 7.4, we used READ TABLE statement to read the first matching record from the internal table  based upon key or index . * In SAP ABAP new syntax, instead of READ TABLE , we can use the table expressions. * We need to use the square bracket [ ], In the square bracket, we need to specify the key or index. * While using table expression, If the table entry does not exist, system throws the exception CX_SY_ITAB_LINE_NOT_FOUND. * Use line_exists statement to check the existence of a record. Report REPORT  zab_rp_read_new . TABLES :   vbak . SELECT-OPTIONS :   s_vbeln  FOR  vbak - vbeln . SELECT  vbeln , erdat , erzet , ernam , auart         FROM  vbak         INTO  TABLE  @DATA ( lt_vbak )          WHERE  vbeln  IN  @s_vbeln . WRITE :   'Index value'  COLOR  5 . READ  T...
Read more