SAP J_1A_CI_NUMBER_GET Function Module for NOTRANSL: Get Number of Credit Invoice

Search SAP Function Modules

J_1A_CI_NUMBER_GET is a standard j 1a ci number get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Get Number of Credit Invoice 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 1a ci number get FM, simply by entering the name J_1A_CI_NUMBER_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function J_1A_CI_NUMBER_GET 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_1A_CI_NUMBER_GET'"NOTRANSL: Get Number of Credit Invoice
  EXPORTING
   IV_BUKRS =  "
   IV_VBELN =  "Sales and Distribution Document Number
   IV_RATNR =  "
*  IV_GET_NEW_NUMBER = ' ' "Checkbox

 IMPORTING
   EV_CI_NUMBER =  "
   EV_CI_ISSUE_DATE =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLJ1AV_001 User-exit branch determination in the delivery document
EXIT_SAPLJ1AV_002 User-exit delivery before official numbering
EXIT_SAPLJ1AV_003 User-exit branch determination in material movement
EXIT_SAPLJ1AV_004 User-exit material movement before official numbering
EXIT_SAPLJ1AV_005 User-exit additional argentine data in the order entry on item level
EXIT_SAPLJ1AV_006 User-exit branch determination in the billing document
EXIT_SAPLJ1AV_007 User-exit billing before official numbering
EXIT_SAPLJ1AV_008 User-exit billing document: check invoice reference

IMPORTING Parameters details for J_1A_CI_NUMBER_GET

IV_BUKRS -

Data type: BUKRS
Optional: No
Call by Reference: Yes

IV_VBELN - Sales and Distribution Document Number

Data type: VBELN
Optional: No
Call by Reference: Yes

IV_RATNR -

Data type: RATNR
Optional: No
Call by Reference: Yes

IV_GET_NEW_NUMBER - Checkbox

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for J_1A_CI_NUMBER_GET

EV_CI_NUMBER -

Data type: J_1ACINUM
Optional: No
Call by Reference: Yes

EV_CI_ISSUE_DATE -

Data type: J_1ACI_ISS_DATE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for J_1A_CI_NUMBER_GET 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 J_1A_CI_NUMBER_GET

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