Additing text in vbak header level

-

      DATA: sales_doc_number TYPE tdobname,
      c_textid         TYPE tdid,
      t_line TYPE STANDARD TABLE OF tline WITH HEADER LINE.

          t_line-tdformat = '*'.

          t_line-tdline  = gs_upload-ref_inv_no.

          APPEND t_line.

          sales_doc_number = gv_salesdocument.
          c_textid = '1000'.
          CALL FUNCTION 'CREATE_TEXT'
            EXPORTING
              fid         = c_textid
              flanguage   = sy-langu
              fname       = sales_doc_number
              fobject     = 'VBBK'
              save_direct = 'X'
              fformat     = '*'
            TABLES
              flines      = t_line
            EXCEPTIONS
              no_init     = 1
              no_save     = 2
              OTHERS      = 3.

CLEAR: c_textid,t_line.

          t_line-tdformat = '*'.

          t_line-tdline  = gs_upload-ref_ino_dat.

          APPEND t_line.

          sales_doc_number = gv_salesdocument.
          c_textid = '1001'.
          CALL FUNCTION 'CREATE_TEXT'
            EXPORTING
              fid         = c_textid
              flanguage   = sy-langu
              fname       = sales_doc_number
              fobject     = 'VBBK'
              save_direct = 'X'
              fformat     = '*'
            TABLES
              flines      = t_line
            EXCEPTIONS
              no_init     = 1
              no_save     = 2
              OTHERS      = 3.

Comments

Post a Comment

Popular posts from this blog

Business senario : FB60 AND FB70 validation and subsituation

-
Image
As per the requirments validation GGB0 and subsituation GGB1 with help to two t-code we can do validation of t-code fb60 or fb70 for this purpose you can go to to standared programs .  there are two t-code for input your validation and subsituation OB28 for validation and OBBH for  subsituation   for subsituation you copy the standared program RGGBR000 in customer namespace and register the program in T80D table and register namespace to V_T80D Program you can change your exit like below   exits - name  =  'RK101' .   exits - param  =  c_exit_param_field .   exits - TITLE  =  TEXT - prb .    APPEND  exits . And second code like below  FORM  upf04 .    IF  BKPF - bukrs  IS  INITIAL .      MESSAGE  'PLease enter COMPANY CODE'  TYPE  'I' .    ENDIF . ENDFORM . and hole code as ...
Read more

MB_MIGO_BADI THIS BADI USED TO POSTING DATA IN MIGO

-
Here this badi used to how to work migo data migration and help to creating magi used to save  and validation of data  MB_DOCUMENT_UPDATE method  IF_EX_MB_MIGO_BADI ~ POST_DOCUMENT .    BREAK-POINT .    IF  is_mkpf - budat < is_mkpf - BLDAT .     sy - ucomm  =  'ENT1' .      MESSAGE  'Posting Date Should Not Be Less Than Document Date'   TYPE  'E'  .      SET SCREEN  syst - dynnr .      LEAVE SCREEN .    ENDIF . endmethod .
Read more

all user exit mv45afzz (implicit user exit )

-
MV45AFZZ this is included here all code put related to sales order creation while creating a sales order  va01 this exit trigger so as per your requirement we can write your code here I going to listed different type exit as per the real requirement you find the code and develop your business scenario INCLUDE MV45AFZZ . Modify Screen VA01/VA02/VA03 How to Activated and Deactivated Screen  Export Memory example While Creating a sales order  How to Call workflow While Creating a sales order  TYPES  :  BEGIN  OF  ty_vbak ,           KVGR1  TYPE  vbak - KVGR1 ,           KVGR2  TYPE  vbak - KVGR2 ,          END  OF  ty_vbak . DATA  :  ls_vbak  TYPE  ty_vbak . IF  sy - tcode  =  'VA02'  and...
Read more