SAP J_1B_BARCODE_CONTROLDIGIT_DDA Function Module for Composition of numerical Barcode for Brazil_DDA









J_1B_BARCODE_CONTROLDIGIT_DDA is a standard j 1b barcode controldigit dda SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Composition of numerical Barcode for Brazil_DDA 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 barcode controldigit dda FM, simply by entering the name J_1B_BARCODE_CONTROLDIGIT_DDA into the relevant SAP transaction such as SE37 or SE38.

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



Function J_1B_BARCODE_CONTROLDIGIT_DDA 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_BARCODE_CONTROLDIGIT_DDA'"Composition of numerical Barcode for Brazil_DDA
EXPORTING
* HOUSE_BANK = "House Bank key
* ACCOUNT_KEY = "Bank account number of the payee
* BANK_KEY = "Bank number of the payee's bank
DUE_DATE_FAC = "Maturity Factor
BARCODE_DAC = "Barcode verify digit
AMOUNT = "Document amount
* FREE_FIELD = "Free Field
* AGENCY = "Agency
* CARTEIRA = "Portfolio
* NOS_NUMERO = "Nosso Numero

IMPORTING
CD1 = "Control digit 1
CD2 = "Control digit 1
CD3 = "Control digit 1
BARCODE_NUM = "Numerical Barcode (47 digits)
.



IMPORTING Parameters details for J_1B_BARCODE_CONTROLDIGIT_DDA

HOUSE_BANK - House Bank key

Data type: CHAR3
Optional: Yes
Call by Reference: Yes

ACCOUNT_KEY - Bank account number of the payee

Data type: REGUH-ZBNKN
Optional: Yes
Call by Reference: Yes

BANK_KEY - Bank number of the payee's bank

Data type: CHAR3
Optional: Yes
Call by Reference: Yes

DUE_DATE_FAC - Maturity Factor

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

BARCODE_DAC - Barcode verify digit

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

AMOUNT - Document amount

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

FREE_FIELD - Free Field

Data type: J_1BXL23
Optional: Yes
Call by Reference: Yes

AGENCY - Agency

Data type: CHAR5
Optional: Yes
Call by Reference: Yes

CARTEIRA - Portfolio

Data type: CHAR3
Optional: Yes
Call by Reference: Yes

NOS_NUMERO - Nosso Numero

Data type: REGUP-XREF3
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for J_1B_BARCODE_CONTROLDIGIT_DDA

CD1 - Control digit 1

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

CD2 - Control digit 1

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

CD3 - Control digit 1

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

BARCODE_NUM - Numerical Barcode (47 digits)

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

Copy and paste ABAP code example for J_1B_BARCODE_CONTROLDIGIT_DDA 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_cd1  TYPE NUMC1, "   
lv_house_bank  TYPE CHAR3, "   
lv_account_key  TYPE REGUH-ZBNKN, "   
lv_cd2  TYPE NUMC1, "   
lv_bank_key  TYPE CHAR3, "   
lv_cd3  TYPE NUMC1, "   
lv_due_date_fac  TYPE NUMC4, "   
lv_barcode_dac  TYPE NUMC1, "   
lv_barcode_num  TYPE C, "   
lv_amount  TYPE NUMC10, "   
lv_free_field  TYPE J_1BXL23, "   
lv_agency  TYPE CHAR5, "   
lv_carteira  TYPE CHAR3, "   
lv_nos_numero  TYPE REGUP-XREF3. "   

  CALL FUNCTION 'J_1B_BARCODE_CONTROLDIGIT_DDA'  "Composition of numerical Barcode for Brazil_DDA
    EXPORTING
         HOUSE_BANK = lv_house_bank
         ACCOUNT_KEY = lv_account_key
         BANK_KEY = lv_bank_key
         DUE_DATE_FAC = lv_due_date_fac
         BARCODE_DAC = lv_barcode_dac
         AMOUNT = lv_amount
         FREE_FIELD = lv_free_field
         AGENCY = lv_agency
         CARTEIRA = lv_carteira
         NOS_NUMERO = lv_nos_numero
    IMPORTING
         CD1 = lv_cd1
         CD2 = lv_cd2
         CD3 = lv_cd3
         BARCODE_NUM = lv_barcode_num
. " J_1B_BARCODE_CONTROLDIGIT_DDA




ABAP code using 7.40 inline data declarations to call FM J_1B_BARCODE_CONTROLDIGIT_DDA

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.

 
 
"SELECT single ZBNKN FROM REGUH INTO @DATA(ld_account_key).
 
 
 
 
 
 
 
 
 
 
 
"SELECT single XREF3 FROM REGUP INTO @DATA(ld_nos_numero).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!