PROJECT_CHECK_CROSS_REF_40 SAP Function module - Customizing subobject list cross-reference check

PROJECT_CHECK_CROSS_REF_40 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name PROJECT_CHECK_CROSS_REF_40 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SCI3
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM PROJECT_CHECK_CROSS_REF_40 - PROJECT CHECK CROSS REF 40

CALL FUNCTION 'PROJECT_CHECK_CROSS_REF_40' "Customizing subobject list cross-reference check
  EXPORTING
    project =                   " sim1_types-project
    structure_id =              " ttree-id
    node_id =                   " tnode01-node_id
    doc_cls =                   " dsyas-child_cls
    doc_obj =                   "
*   start_workflow = ' '        "
  IMPORTING
    used_in_other_projects =    "
* TABLES
*   subobjects =                " objsub
    .  "  PROJECT_CHECK_CROSS_REF_40

ABAP code example for Function Module PROJECT_CHECK_CROSS_REF_40

The ABAP code below is a full code listing to execute function module PROJECT_CHECK_CROSS_REF_40 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_used_in_other_projects  
 
 TYPE STRING
,
it_subobjects  
 
 TYPE STANDARD TABLE OF OBJSUB,"TABLES PARAM
wa_subobjects
 
 LIKE LINE OF it_subobjects
.



DATA(ld_project) = some text here
 

SELECT single ID 
  FROM TTREE 
  INTO @DATA(ld_structure_id).

 

SELECT single NODE_ID 
  FROM TNODE01 
  INTO @DATA(ld_node_id).

 

SELECT single CHILD_CLS 
  FROM DSYAS 
  INTO @DATA(ld_doc_cls).


DATA(ld_doc_obj) = 'some text here'.

DATA(ld_start_workflow) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_subobjects to it_subobjects.
.

CALL FUNCTION 'PROJECT_CHECK_CROSS_REF_40'
  EXPORTING
    project =                    ld_project
    structure_id =               ld_structure_id
    node_id =                    ld_node_id
    doc_cls =                    ld_doc_cls
    doc_obj =                    ld_doc_obj
*   start_workflow =             ld_start_workflow
  IMPORTING
    used_in_other_projects =     ld_used_in_other_projects
* TABLES
*   subobjects =                 it_subobjects
    .  "  PROJECT_CHECK_CROSS_REF_40

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_used_in_other_projects
 
 TYPE STRING ,
ld_project
 
 TYPE SIM1_TYPES-PROJECT ,
it_subobjects
 
 TYPE STANDARD TABLE OF OBJSUB ,
wa_subobjects
 
 LIKE LINE OF it_subobjects,
ld_structure_id
 
 TYPE TTREE-ID ,
ld_node_id
 
 TYPE TNODE01-NODE_ID ,
ld_doc_cls
 
 TYPE DSYAS-CHILD_CLS ,
ld_doc_obj
 
 TYPE STRING ,
ld_start_workflow
 
 TYPE STRING .



ld_project = some text here 

"populate fields of struture and append to itab
append wa_subobjects to it_subobjects.

SELECT single ID 
  FROM TTREE 
  INTO ld_structure_id.


SELECT single NODE_ID 
  FROM TNODE01 
  INTO ld_node_id.


SELECT single CHILD_CLS 
  FROM DSYAS 
  INTO ld_doc_cls.

ld_doc_obj = 'some text here'.
ld_start_workflow = 'some text here'.