SAP J_1B_CTE_READ_PAR_MAP Function Module for Find CTe-partner mapping
J_1B_CTE_READ_PAR_MAP is a standard j 1b cte read par map SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find CTe-partner mapping 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 j 1b cte read par map FM, simply by entering the name J_1B_CTE_READ_PAR_MAP into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1B_CTE
Program Name: SAPLJ_1B_CTE
Main Program: SAPLJ_1B_CTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1B_CTE_READ_PAR_MAP 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 'J_1B_CTE_READ_PAR_MAP'"Find CTe-partner mapping.
EXPORTING
I_NFTYPE = "Nota Fiscal Type
I_PARVW = "Nota Fiscal Partner Function
IMPORTING
E_PAR_MAP = "CT-e: Mapping to NF-e Partner Function
EXCEPTIONS
MAPPING_NOT_FOUND = 1
IMPORTING Parameters details for J_1B_CTE_READ_PAR_MAP
I_NFTYPE - Nota Fiscal Type
Data type: J_1BNFTYPEOptional: No
Call by Reference: Yes
I_PARVW - Nota Fiscal Partner Function
Data type: J_1BPARVWOptional: No
Call by Reference: Yes
EXPORTING Parameters details for J_1B_CTE_READ_PAR_MAP
E_PAR_MAP - CT-e: Mapping to NF-e Partner Function
Data type: J_1BCTE_PAR_MAPOptional: No
Call by Reference: Yes
EXCEPTIONS details
MAPPING_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1B_CTE_READ_PAR_MAP 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.| DATA: | ||||
| lv_i_nftype | TYPE J_1BNFTYPE, " | |||
| lv_e_par_map | TYPE J_1BCTE_PAR_MAP, " | |||
| lv_mapping_not_found | TYPE J_1BCTE_PAR_MAP, " | |||
| lv_i_parvw | TYPE J_1BPARVW. " |
|   CALL FUNCTION 'J_1B_CTE_READ_PAR_MAP' "Find CTe-partner mapping |
| EXPORTING | ||
| I_NFTYPE | = lv_i_nftype | |
| I_PARVW | = lv_i_parvw | |
| IMPORTING | ||
| E_PAR_MAP | = lv_e_par_map | |
| EXCEPTIONS | ||
| MAPPING_NOT_FOUND = 1 | ||
| . " J_1B_CTE_READ_PAR_MAP | ||
ABAP code using 7.40 inline data declarations to call FM J_1B_CTE_READ_PAR_MAP
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