![]() |
T4S4
18.2 C7549 A21431
Teamcenter Gateway for SAP S/4HANA API Reference
|
Functions | |
callBAPI_REFSETOFOPERATIONS_CREATE args | |
Calls the BAPI_REFSETOFOPERATIONS_CREATE ABAP via JCo The following lines are extracted from the SAP function module documentation, Copyright SAP AG. More... | |
callBAPI_REFSETOFOPR_EXISTENCE_CHK TaskListGroup GroupCounter ?ValidFrom? ?ValidTo? args | |
Calls the BAPI_REFSETOFOPR_EXISTENCE_CHK ABAP via JCo The following lines are extracted from the SAP function module documentation, Copyright SAP AG. More... | |
TPSAP::REFSETOFOPERATIONS::callBAPI_REFSETOFOPERATIONS_CREATE | args | ||
Calls the BAPI_REFSETOFOPERATIONS_CREATE ABAP via JCo The following lines are extracted from the SAP function module documentation, Copyright SAP AG.
_______________________________________________... | | FUNCTIONALITY | _____________ | | This method serves to create reference operation sets with all their | subordinated objects. | Here, you can generate a key date view as well as the complete history | of a reference operation set. The latter is particularly useful for | data transfers from non-SAP systems. | | EXAMPLE | _______ | | You want to create a reference operation set with its operations and | inspection characteristics on the key date 01.01.2000. | You generate an entry for each object in the following table by always | entering the date 01.01.2000 in the attribute VALID_FROM: | TASK | | Enter the relevant task list header data here. The attributes | TASK_LIST_GROUP and GROUP_COUNTER only have to be supplied if you work | with external number assignment. For internal number assignment the | task list group and the group counter are determined automatically. | OPERATION | | You generate an entry for each operation in this table. To identify the | operations, you have to enter an external operation identifier in the | field OPERATION_ID. This identifier has to contain at least one | character that is not a number (such as VORG0010). You only have to | supply the TASK_LIST_GROUP and GROUP_COUNTER in the case of external | number assignment. | INSPCHARACTERISTIC | | You generate an entry for each inspection characteristic in this table. | To identify the inspection characteristics you have to enter an | inspection characteristic number in the field INSPCHAR. You can create | inspection characteristics with or without reference to a master | inspection characteristic. In the field CHA_MASTER_IMPORT_MODUS (Modus | for the reference to the master inspection characteristic) enter the | reference to the master inspection characteristic: 'L' for reference. | In this case, the master inspection characteristic has to be completely | maintained. In the parameter INSPCHARACTERISTIC you only have to supply | those fields that could not be copied from the master inspection | characteristic; 'C' for copy the data from the master inspection | characteristic into the inspection characteristic, 'N' for create a | lockable and unlockable reference to the master inspection | characteristic without a data transfer from the master inspection | characteristic. In this case manually fill out all fields in the | parameter INSPCHARACTERISTIC. | You can either transfer the inspection characteristic control indicator | directly from the master inspection characteristic, enter it | individually or in the field PRESET_CTRL_INDS_KEY you enter a key for | the control indicator if you have stored this key in Customizing. | If you have individually entered a control indicator, note the | following special features: | SCOPE_IND: Inspection scope. This indicator can have different | characteristics: | You set " " for: Free inspection scope | You set "<" for: Smaller inspection scope permitted | You set ">" for: Larger inspection scope permitted | You set "=" for: Specified inspection scope | RESULT_RECORDING_TYPE: Record entry type. This indicator can have | different characteristics: | You set "-" for: No record entry | You set "*" for: Classified record entry | You set "+" for: Single record entry | You set " " for: Summarized record entry | DOCU_REQU: Documentation required for check results. This indicator can | have different characteristics: | You set " " for: No documention required | You set "." for: Documentation for rejection | You set "+" for: Document all check results | CONFIRMATION_CATEGORY Characteristic category | You set " " for: Optional characteristic | You set "+" for: Limited to the acceptance of the previous mandatory | characteristic | You set "-" for: Limited to the rejection of the previous mandatory | characteristic | You set "X" for: Mandatory characteristic | PRINT_IND: Print control | This indicator can have different characteristics: | You set " " for: Print | You set "x" for: Do not print | You set "*" for: Do not print at skip | | If you want to assign an inspection equipment to the inspection | characteristic in the field ITEM_NO_OF_PRODUCTION_RESOURCE, note that | this has to be assigned to the operation in the PARAMETER | PRODUCTIONRESOURCE. | | | HINTS | _____ | | Provided that during the data transfer no errors can be found, the | export parameters GROUP and GROUPCOUNTER contain the key for the | generated reference operation set. To secure the data in the database, | you now have to carry out a COMMIT WORK. | All errors that occur are logged in the external paramter RETURN. In | the case of inconsistencies, the entire reference operation set to be | generated is rejected. | | FURTHER_SOURCES_OF_INF | ______________________ | | ..._______________________________________________
References T4X::CORE::getSessionLogChannel(), TPSAP::performSapCall(), tpwrite(), and SYSBase::unixid().
TPSAP::REFSETOFOPERATIONS::callBAPI_REFSETOFOPR_EXISTENCE_CHK | TaskListGroup GroupCounter ?ValidFrom? ?ValidTo? args | ||
Calls the BAPI_REFSETOFOPR_EXISTENCE_CHK ABAP via JCo The following lines are extracted from the SAP function module documentation, Copyright SAP AG.
_______________________________________________... | | FUNCTIONALITY | _____________ | | This module checks whether the reference operation set specified by the | task list group (GROUP) and the group counter (GROUPCOUNTER) exists. As | additional criteria you can enter the selection period to be used. In | this case, the system checks whether the specified reference operation | set exists in the given selection period. | | EXAMPLE | _______
| HINTS | _____ | | Note that the function module merely provides information about whether | the specified reference operation set exists in the selection period or | not. It does not say anything about the effectivity of the reference | operation set within this period | | FURTHER_SOURCES_OF_INF | ______________________ | | ..._______________________________________________
TaskListGroup | |
GroupCounter | |
ValidFrom | (optional - empty) |
ValidTo | (optional - 99991231) |
TaskListGroup |
References TPSAP::performSapCall().