SAP J_1BNFE_CCE_DISPLAY Function Module for Display Correction Letter
J_1BNFE_CCE_DISPLAY is a standard j 1bnfe cce display SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Correction Letter 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 1bnfe cce display FM, simply by entering the name J_1BNFE_CCE_DISPLAY into the relevant SAP transaction such as SE37 or SE38.
Function Group: J_1B_NFE_EVENT
Program Name: SAPLJ_1B_NFE_EVENT
Main Program: SAPLJ_1B_NFE_EVENT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_1BNFE_CCE_DISPLAY 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_1BNFE_CCE_DISPLAY'"Display Correction Letter.
EXPORTING
IV_DOCNUM = "Document Number
IV_SEQNUM = "Event Sequence Number
EXCEPTIONS
NOT_EXISTING = 1
IMPORTING Parameters details for J_1BNFE_CCE_DISPLAY
IV_DOCNUM - Document Number
Data type: J_1BDOCNUMOptional: No
Call by Reference: Yes
IV_SEQNUM - Event Sequence Number
Data type: J_1BNFE_EVENT_SEQNOOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_EXISTING - CC-e sequence does not exist
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for J_1BNFE_CCE_DISPLAY 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_iv_docnum | TYPE J_1BDOCNUM, " | |||
| lv_not_existing | TYPE J_1BDOCNUM, " | |||
| lv_iv_seqnum | TYPE J_1BNFE_EVENT_SEQNO. " |
|   CALL FUNCTION 'J_1BNFE_CCE_DISPLAY' "Display Correction Letter |
| EXPORTING | ||
| IV_DOCNUM | = lv_iv_docnum | |
| IV_SEQNUM | = lv_iv_seqnum | |
| EXCEPTIONS | ||
| NOT_EXISTING = 1 | ||
| . " J_1BNFE_CCE_DISPLAY | ||
ABAP code using 7.40 inline data declarations to call FM J_1BNFE_CCE_DISPLAY
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