SAP EXP_JIB_MAPPING Function Module for Joint Venture - JIB Mapping for Billing

Search SAP Function Modules

EXP_JIB_MAPPING is a standard exp jib mapping SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Joint Venture - JIB Mapping for Billing processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for exp jib mapping FM, simply by entering the name EXP_JIB_MAPPING into the relevant SAP transaction such as SE37 or SE38.

Function Group: GJVB
Program Name: SAPLGJVB
Main Program: SAPLGJVB
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXP_JIB_MAPPING pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'EXP_JIB_MAPPING'"Joint Venture - JIB Mapping for Billing
  EXPORTING
   I_BUKRS =  "Company Code
*  I_RPRCTR =  "Profit Center
   I_EGRUP =  "Equity Group
   I_EXP_NAT_DET =  "Table : Structure T8JVB03
   I_JIB_MAP =  "JIB vs Natural Code Indicator
   I_KOKRS =  "Controlling Area
   I_VENTURE =  "Venture
*  I_TTYPE = '   ' "
*  I_DATE =  "
*  I_NO_MESSAGE = ' ' "No messages

 IMPORTING
   E_EXP_NAT_DET =  "
   E_PR_TYPE =  "
   E_CC_TYPE =  "
   E_OR_TYPE =  "

.

IMPORTING Parameters details for EXP_JIB_MAPPING

I_BUKRS - Company Code

Data type: T001-BUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_RPRCTR - Profit Center

Data type: JVTO1-RPRCTR
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_EGRUP - Equity Group

Data type: T8JF-EGRUP
Optional: No
Call by Reference: No ( called with pass by value option)

I_EXP_NAT_DET - Table : Structure T8JVB03

Data type: T8JVB03
Optional: No
Call by Reference: No ( called with pass by value option)

I_JIB_MAP - JIB vs Natural Code Indicator

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

I_KOKRS - Controlling Area

Data type: CSKS-KOKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_VENTURE - Venture

Data type: T8JV-VNAME
Optional: No
Call by Reference: No ( called with pass by value option)

I_TTYPE -

Data type: JVTO1-RANBWA
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DATE -

Data type: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NO_MESSAGE - No messages

Data type:
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for EXP_JIB_MAPPING

E_EXP_NAT_DET -

Data type: T8JVB03
Optional: No
Call by Reference: No ( called with pass by value option)

E_PR_TYPE -

Data type: PRPS-OTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

E_CC_TYPE -

Data type: CSKS-JV_OTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

E_OR_TYPE -

Data type: AUFK-OTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for EXP_JIB_MAPPING Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM EXP_JIB_MAPPING

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects