SAP CACS00_OUTBOUND_PRC_1099 Function Module for NOTRANSL: BTE: Umfeldnachbereitung eines Provisionsfall









CACS00_OUTBOUND_PRC_1099 is a standard cacs00 outbound prc 1099 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: BTE: Umfeldnachbereitung eines Provisionsfall 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 cacs00 outbound prc 1099 FM, simply by entering the name CACS00_OUTBOUND_PRC_1099 into the relevant SAP transaction such as SE37 or SE38.

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



Function CACS00_OUTBOUND_PRC_1099 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 'CACS00_OUTBOUND_PRC_1099'"NOTRANSL: BTE: Umfeldnachbereitung eines Provisionsfall
  EXPORTING
   I_APPL_VERSION =  "Version of Generated Application
   IFLG_MASS_PROCESS =  "Mass Processing? (See Documentation)
   IFLG_SIMULATION =  "Process should be carried out in simulation mode
   I_CASE =  "Reported Commission Case (See Documentation)
   I_DOC_HEAD =  "Resulting Document Header

TABLES
   I_PARTICIPATION =  "Reported Participation(s) in Case
   I_DOC_REMDETAIL =  "Comn: Detail Items for Remuneration Rows
   I_DOC_SETTLEMENT =  "Determined Due Dates for Settlement
*  I_DOC_PARTICIPATION =  "Participation of Commission Document
*  I_DOC_INVESTIGATION =  "Participant in Commission Document
*  I_DOC_RELATIONS =  "Commission Document: Relationships Between Participants
*  I_DOC_ACTIVITY =  "Commission Document: Activities
*  I_DOC_OBJECTDATA =  "Commission Document: Object Data
   I_INVESTIGATION =  "Reported Participants in Participation
   I_RELATIONS =  "Reported Relationships Between Participants
   I_ACTIVITY =  "Reported Activities for Case
   I_OBJECTDATA =  "Reported Object Descriptions for Activities
   I_LINES =  "Reported Variances (Special Commission) for Case
   I_BUNDLE =  "Rebundling Order for Triggering Subobjects
   I_DOC_VALUATION =  "Determined Valuations for ComnDoc
   I_DOC_REMUNERATION =  "Determined Remuneration for ComnDoc

EXCEPTIONS
   NO_DESTINATION = 1    NO_COMPONENT_ACTIVE = 2    ERROR_MULTIPLE_SELECTION = 3
.



IMPORTING Parameters details for CACS00_OUTBOUND_PRC_1099

I_APPL_VERSION - Version of Generated Application

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

IFLG_MASS_PROCESS - Mass Processing? (See Documentation)

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

IFLG_SIMULATION - Process should be carried out in simulation mode

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

I_CASE - Reported Commission Case (See Documentation)

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

I_DOC_HEAD - Resulting Document Header

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

TABLES Parameters details for CACS00_OUTBOUND_PRC_1099

I_PARTICIPATION - Reported Participation(s) in Case

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

I_DOC_REMDETAIL - Comn: Detail Items for Remuneration Rows

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

I_DOC_SETTLEMENT - Determined Due Dates for Settlement

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

I_DOC_PARTICIPATION - Participation of Commission Document

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

I_DOC_INVESTIGATION - Participant in Commission Document

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

I_DOC_RELATIONS - Commission Document: Relationships Between Participants

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

I_DOC_ACTIVITY - Commission Document: Activities

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

I_DOC_OBJECTDATA - Commission Document: Object Data

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

I_INVESTIGATION - Reported Participants in Participation

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

I_RELATIONS - Reported Relationships Between Participants

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

I_ACTIVITY - Reported Activities for Case

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

I_OBJECTDATA - Reported Object Descriptions for Activities

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

I_LINES - Reported Variances (Special Commission) for Case

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

I_BUNDLE - Rebundling Order for Triggering Subobjects

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

I_DOC_VALUATION - Determined Valuations for ComnDoc

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

I_DOC_REMUNERATION - Determined Remuneration for ComnDoc

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

EXCEPTIONS details

NO_DESTINATION - Error in Remote Function Call

Data type:
Optional: No
Call by Reference: Yes

NO_COMPONENT_ACTIVE - No active component

Data type:
Optional: No
Call by Reference: Yes

ERROR_MULTIPLE_SELECTION - More than one entry exists

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACS00_OUTBOUND_PRC_1099 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_appl_version  TYPE CACSGENVERSION, "   
lv_no_destination  TYPE CACSGENVERSION, "   
lt_i_participation  TYPE STANDARD TABLE OF CACS00_PAR, "   
lt_i_doc_remdetail  TYPE STANDARD TABLE OF CACS00_DOCDT, "   
lt_i_doc_settlement  TYPE STANDARD TABLE OF CACS00_DOCSE, "   
lt_i_doc_participation  TYPE STANDARD TABLE OF CACS00_DOCPAR, "   
lt_i_doc_investigation  TYPE STANDARD TABLE OF CACS00_DOCINV, "   
lt_i_doc_relations  TYPE STANDARD TABLE OF CACS00_DOCREL, "   
lt_i_doc_activity  TYPE STANDARD TABLE OF CACS00_DOCACT, "   
lt_i_doc_objectdata  TYPE STANDARD TABLE OF CACS00_DOCOBJ, "   
lt_i_investigation  TYPE STANDARD TABLE OF CACS00_INV, "   
lv_iflg_mass_process  TYPE BOOLEAN_FLG, "   
lv_no_component_active  TYPE BOOLEAN_FLG, "   
lt_i_relations  TYPE STANDARD TABLE OF CACS00_REL, "   
lv_iflg_simulation  TYPE CACSSIMULATION, "   
lv_error_multiple_selection  TYPE CACSSIMULATION, "   
lv_i_case  TYPE CACS00_CAS, "   
lt_i_activity  TYPE STANDARD TABLE OF CACS00_ACT, "   
lv_i_doc_head  TYPE CACS00_DOCHD, "   
lt_i_objectdata  TYPE STANDARD TABLE OF CACS00_OBJ, "   
lt_i_lines  TYPE STANDARD TABLE OF CACS00_LIN, "   
lt_i_bundle  TYPE STANDARD TABLE OF CACS00_BDL, "   
lt_i_doc_valuation  TYPE STANDARD TABLE OF CACS00_DOCVA, "   
lt_i_doc_remuneration  TYPE STANDARD TABLE OF CACS00_DOCRE. "   

  CALL FUNCTION 'CACS00_OUTBOUND_PRC_1099'  "NOTRANSL: BTE: Umfeldnachbereitung eines Provisionsfall
    EXPORTING
         I_APPL_VERSION = lv_i_appl_version
         IFLG_MASS_PROCESS = lv_iflg_mass_process
         IFLG_SIMULATION = lv_iflg_simulation
         I_CASE = lv_i_case
         I_DOC_HEAD = lv_i_doc_head
    TABLES
         I_PARTICIPATION = lt_i_participation
         I_DOC_REMDETAIL = lt_i_doc_remdetail
         I_DOC_SETTLEMENT = lt_i_doc_settlement
         I_DOC_PARTICIPATION = lt_i_doc_participation
         I_DOC_INVESTIGATION = lt_i_doc_investigation
         I_DOC_RELATIONS = lt_i_doc_relations
         I_DOC_ACTIVITY = lt_i_doc_activity
         I_DOC_OBJECTDATA = lt_i_doc_objectdata
         I_INVESTIGATION = lt_i_investigation
         I_RELATIONS = lt_i_relations
         I_ACTIVITY = lt_i_activity
         I_OBJECTDATA = lt_i_objectdata
         I_LINES = lt_i_lines
         I_BUNDLE = lt_i_bundle
         I_DOC_VALUATION = lt_i_doc_valuation
         I_DOC_REMUNERATION = lt_i_doc_remuneration
    EXCEPTIONS
        NO_DESTINATION = 1
        NO_COMPONENT_ACTIVE = 2
        ERROR_MULTIPLE_SELECTION = 3
. " CACS00_OUTBOUND_PRC_1099




ABAP code using 7.40 inline data declarations to call FM CACS00_OUTBOUND_PRC_1099

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



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!