SAP JV_EDI_JVUSBI_OP_STMT Function Module for JV EDI Billing - Operating Exp. Statement for US processing

Search SAP Function Modules

JV_EDI_JVUSBI_OP_STMT is a standard jv edi jvusbi op stmt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for JV EDI Billing - Operating Exp. Statement for US processing 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 jv edi jvusbi op stmt FM, simply by entering the name JV_EDI_JVUSBI_OP_STMT into the relevant SAP transaction such as SE37 or SE38.

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

Function JV_EDI_JVUSBI_OP_STMT 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 'JV_EDI_JVUSBI_OP_STMT'"JV EDI Billing - Operating Exp. Statement for US processing
  EXPORTING
   OBJECT_KEY =  "Company/Fund Curr/Year/Period
   PARTOUT =  "EDI partner information for the outbox

 IMPORTING
   IDOC_CONTROL =  "Control record for EDI
   OBJECT_TYPE =  "Object type for the workflow link

EXCEPTIONS
   EDI_DOCUMENT_NOT_CLOSED = 1    EDI_DOCUMENT_NOT_OPENED = 2    EDI_SEGMENT_CREATE_ERROR = 3    PARAMETER_ERROR = 4    PARTNER_DATA_ERROR = 5    DATA_NOT_RELEVANT_FOR_SENDING = 6 

.

IMPORTING Parameters details for JV_EDI_JVUSBI_OP_STMT

OBJECT_KEY - Company/Fund Curr/Year/Period

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

PARTOUT - EDI partner information for the outbox

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

EXPORTING Parameters details for JV_EDI_JVUSBI_OP_STMT

IDOC_CONTROL - Control record for EDI

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

OBJECT_TYPE - Object type for the workflow link

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

EXCEPTIONS details

EDI_DOCUMENT_NOT_CLOSED - Error when closing intermediate document

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

EDI_DOCUMENT_NOT_OPENED - Error when opening intermediate document

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

EDI_SEGMENT_CREATE_ERROR - Error when attemting to create a segment

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

PARAMETER_ERROR - Incorrect parameters during transfer of segmen

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

PARTNER_DATA_ERROR - Partner neither has ext. number nor address

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

DATA_NOT_RELEVANT_FOR_SENDING - Data not relevant for sending

Data type:
Optional: No
Call by Reference: Yes

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

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