Kontakt

Ansicht
Dokumentation

RCP301_RECIPES_READ - NOTRANSL: RMS-RCP: Lesen von Rezeptobjekten

RCP301_RECIPES_READ - NOTRANSL: RMS-RCP: Lesen von Rezeptobjekten

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

This functionality is part of the Application Programming Interface in RMS for recipe objects and is used to read recipe data.

Which Recipe Data is Read?

To specify the recipe objects for which the SAP System reads data, the IT_KEY table must contain records that have a value in the GUID field.

This GUID can identify the following:

  • GUID recipe
  • GUID building block for process element (process, stage, operation, action)
  • GUID building block for equipment requirement

If an entry in the IT_KEY table contains values, this GUID is used to select the relevant data. If the GUID is not found, or if the object is a dependent object for a recipe or building block, the system writes an error message to the ET_ERROR table.

Which Data is Read From the Recipe Objects?

The recipe data that is read is determined by the individual indicators in the IS_ENTITY_FLAGS structure, whereby an indicator corresponds to one or more output tables as follows:

FLG_RCP   ET_RCP
FLG_PRO   ET_PRO
FLG_PST   ET_PST
FLG_POP   ET_POP
FLG_PAC   ET_PAC
FLG_EQR   ET_EQR
FLG_STX   ET_STX
FLG_RCTX   ET_RCTX
FLG_LTX   ET_LTX
FLG_DOC   ET_DOC
FLG_CLA   ET_CLA
FLG_IDENT   ET_IDENT
FLG_ASCOPE   ET_ASCOPE
FLG_REPLACE   ET_REPLACE
FLG_REL_FRM   ET_REL_FRM
FLG_REL_FIT   ET_REL_FIT
FLG_REL_MR   ET_REL_MR
FLG_REL_OP   ET_OP_SUC
  ET_OP_PRE
FLG_PP   ET_PP

When an indicator is set to TRUE, the relevant data is placed in the associated output table(s).

The output table ET_AENNR contains all the change statuses of a recipe, irrespective of the validity period for which the data was read. This data is provided for information purposes only, and is always filled by the API.

How is the Data Read, and Why?

The I_DATA_SCENARIO determines how the recipe objects are read, that is, "to be displayed"('D')", "to be changed ('U')", for "for information purposes ('I')".

Interval-Based Reading and Writing

Using the Application Programming Interface function modules (API function modules) for reading, creating, changing, and deleting data records, you can process data not only for a specific date but also for an entire interval. In other words, you can process all the data records that are valid on at least one date in the specified interval in one Logical Unit of Work (LUW). The API function module for reading data records uses the following parameters for this purpose:

  • I_VALFROM
  • I_VALTO

If only the I_VALFROM parameter contains an entry, the system reads the data for a specific date. If both fields are filled, the system reads the data for the specified interval. The I_FLG_RANGE_INDEP field also affects how the data is read.

If the indicator is set to TRUE, a data entry is always returned, even if it is not valid within the specified interval or on the specified date. (If the recipe object has change statuses, the change status that is nearest the key date or interval is returned.)

If this indicator is not set, the system writes an error message to the ET_ERROR table if the recipe object was not found within the specified period or on the specified key date.

Hierarchy Information

Every table contains information on the hierarchy level of the current entry:

  • GUID
  • AENNR
  • GUID_MAST
  • GUID_ROOT
  • AENNR_ROOT

The GUID and AENNR fields identify the current entry.

The GUID_MAST field identifies the direct parent.

The GUID_ROOT and AENNR_ROOT fields identify the top parent.

These entries enable the recipe objects and associated dependent objects to be determined.

Example: Reading a recipe with dependent stages and operations.

In the stage entry:

  • The GUID, AENNR field contains the actual identification
  • The GUID_MAST field contains the recipe identification
  • The GUID_ROOT, AENNR_ROOT field contains the recipe identification

In the operation entry:

  • The GUID, AENNR field contains the actual identification
  • The GUID_MAST field contains the stage identification
  • The GUID_ROOT, AENNR_ROOT field contains the recipe identification

Authorizations

If read authorizations have not been assigned for an entry, the system writes a log entry to the ET_NOT_AUTH table.

Troubleshooting

Any messages that are output (errors, warnings, success messages, and so on) are collected in the ET_ERROR table.

Further Information

Type group RCP31 contains constants for the function call.

Example

Notes

Further information





Parameters

ET_AENNR
ET_ASCOPE
ET_CLA
ET_DOC
ET_EQR
ET_ERROR
ET_IDENT
ET_LTX
ET_NO_AUTH
ET_OP_PRE
ET_OP_SUC
ET_PAC
ET_POP
ET_PP
ET_PP_N
ET_PRO
ET_PST
ET_RCP
ET_RCTX
ET_REL_FIT
ET_REL_FRM
ET_REL_MR
ET_REPLACE
ET_STX
ET_USTATUS
IS_ENTITY_FLAGS
IT_DEPKEY
IT_KEY
I_DATA_SCENARIO
I_FLG_AUTH_F4
I_FLG_LANGUAGE
I_FLG_NO_AUTH_CHECK
I_FLG_RANGE_INDEP
I_VALFROM
I_VALTO

Exceptions

ERROR

Function Group

RCP301

General Material Data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8509 Date: 20240523 Time: 164000     sap01-206 ( 105 ms )