Call BP Transaction by passing Business partner number

-

Use the Below code to call BP Transaction in the place of obsolete Customer/Vendor related transactions in  SAP. 

 DATA:

    lv_request TYPE REF TO cl_bupa_navigation_request,

    lv_options TYPE REF TO cl_bupa_dialog_joel_options,

    lv_partner TYPE bu_partner,

    lv_partner_role TYPE bus_roles,

    lv_start_tab TYPE BUS_NAVIGATION-BUPA-SUB_HEADER_TAB,

    lv_bup_main TYPE bus_bupr_maintenance.


* set start-up navigation-----------------------------------------------

  lv_partner = <fs_row>-kunnr.

  lv_partner_role-role = 'FLCU01'.  “ Pass the Role

  lv_start_tab = 'CVIC01'.          “ Start tab

  CREATE OBJECT lv_request.


*set partner maintenance

  CALL METHOD lv_request->set_maintenance_id

    EXPORTING

      iv_value = lv_request->gc_maintenance_id_partner.


*set partner number to start with (in case of a guid just use the method

*set_partner_guid)

  CALL METHOD lv_request->set_partner_number( im_partner ). “ pass BP number from input


*set the partner role to start with

  CALL METHOD lv_request->set_bupa_partner_role( lv_partner_role ).


*set the activity you want the user to start the maintenance with

  CALL METHOD lv_request->set_bupa_activity

    EXPORTING

      iv_value = lv_request->gc_activity_display.


  CALL METHOD lv_request->set_bupa_sub_header_tab

    EXPORTING

      iv_value = lv_start_tab.


*set start-up options----

  CREATE OBJECT lv_options.


*start the transaction with an invisible locator

  CALL METHOD lv_options->set_locator_visible( space ).


*don't allow navigations to other partners

  CALL METHOD lv_options->set_navigation_disabled( abap_true ).

  CALL METHOD lv_options->set_bupr_create_not_allowed( abap_true ).


  lv_bup_main-create_allowed = abap_true.

  lv_bup_main-change_allowed = abap_true.

  lv_bupr_main-delete_allowed = abap_true.


  CALL METHOD lv_options->set_bupr_maintenance( lv_bup_main ).


  CALL METHOD lv_options->set_activity_switching_off( space ).


*Call the business partner maintenance---

*with those parameters

  CALL METHOD cl_bupa_dialog_joel=>start_with_navigation

    EXPORTING

      iv_request = lv_request

      lv_options = lv_options

    EXCEPTIONS

      OTHERS     = 1.


Comments

Post a Comment

Popular posts from this blog

SAP ABAP-Internal Table Operations and Example Program

-
Image
Internal Table Operations: Below are the Operations of Internal Table Append Insert Delete Modify Describe Sort Refresh Clear Free Loop … Endloop Read Table   1.Append   - to append the workarea record at the last position of internal table. we can append:   a. single record   b. multiple records a. single record (one -> Many / Workarea-> Internal table) Syntax:   APPEND <WORKAREA NAME> TO <INTERNAL TABLE NAME>. Example:    wa_data-PATIENTID               = 9999.    wa_data-PATIENTNAME    = 'Addition1'.    wa_data-HOSPITALNAME = 'Alpha Hospital'.      APPEND wa_data to IT_DATA.    CLEAR wa_data.     b. Multiple records (Many->Many / Internal table1 to internal table2) Syntax: APPEND LINES OF <Internal table name1> to <Internal table name2>. Note: While appending 1 internal table data with another interna
Read more

HR ABAP Interview Questions and Answers

-
1)        Difference Between ABAP & HR-ABAP ? ABAP and HR-ABAP are almost similar but HR-ABAP has some different approach to program like logical      database (like PNP & PCH) are extensively used in HR-ABAP. Infotypes and Infotypes related tables are used in HR-ABAP. Some specific comments like provide ...endprovide are used in HR-ABAP but not generally in ABAP. 2)        Infotype ? The data fields of HR master data, time management and recruitment are grouped logically into information types or infotypes for short. Examples of infotypes are "Family/Related Person", "Organizational Assignment, "Basic Pay". Infotype Category’s: o     Infotypes 0000 - 0999 - HR master data   and sometimes for applicant data o     Infotypes 1000 - 1999 - organizational management o     Infotypes 2000 - 2999 - time data o     Infotypes 4000 - 4999 - applicant data o     Infotypes 9000 - 9999 - customers 3)        Subtype ?   Subtypes are
Read more

BDC (Batch Data Communication) - SAP ABAP

-
Image
BDC (Batch Data Communication) Batch input is a standard technique used to transfer large volumes of data into an SAP system. The advantage of batch input is that all the transaction-level checks can be performed on the data and then the data is updated through the transactions (Via Screens). Data transfer project involves the following steps:  1. Identifying the data that needs to be transferred to the SAP. 2.Record the screen fields using transaction: SHDB & generate a program from it. 3. Write the BDC program separately by making use of Recoding code (Step no:2) 4. If required, Convert the data while passing from Non-SAP to SAP (External to Internal). 5. Handle various errors/messages in program as per requirement. 6.Validate the data while processing. 7 . Process the program and verify the transferred data in SAP. 8. Set the data transfer frequency as per business requirement. Note: Batch input programs allow us to capture all t
Read more