Ansicht
Dokumentation

/SAPAPO/FOT_GET_PPE - FOT - Rudi - get ppe

BAL Application Log Documentation   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Functionality

This function module will return for a given location / product combination several ouptut tables which are described in detail below. If you specify a production version only the information for this production version will be returned.

Example

ET_PPE (important fields): Table with production versions

(--> basically these are the production version entries in /sapapo/trprod)

structure: /SAPAPO/S_TRPROD (Structure for Table TRPROD)

,,- NAME: production version

,,- PPEGUID: type PVS_GUID (Raw 16) (Internal Identification for PVS Objects)

ET_HEADER (important fields): --> joined DB view of PPEHDR + PPELNK + PPEOBJ (see below for DB tables)

type V_PPEHDR (Database View of the Access Object)

,,- PPENAME: production version

,,- PPEGUID: type PVS_GUID (Raw 16) (Internal Identification for PVS Objects)

,,- OBJID: type PVS_OBJID (Char 32) (Internal Identification of an iPPE Object)

,,- PPEUSE: Usage in iPPE

,,- OBJTYPE: type PPE_OBJTYPE (Object Type of the iPPE Header Object )

,,- PGUID: type PVS_GUID (same as PPEGUID)

,,- OTYPE: type PVS_OTYPE (iPPE Object Type),

,,- PVGUID: type PVS_GUID (same as PPEGUID)

,,- APPLOBJ_TYPE: type PPE_APPLOBJ_TYPE (iPPE Application Object Type)

PPEGUID: ID for iPPE access object. Basically it is the production version in APO (TA: PPEHDR02)

OBJID: ID for the objects within an iPPE access object. For the product structure it is the MATID.

If you maintained a product structure and a process structure in your iPPE access object the table ET_HEADER will have 2 entries.

ET_RP_SORT: Table with sorted reporting points

(sorting criteria is predecessor-successor relationship in ET_RP_REL)

ET_RP_REL: predecessor-successor relationship of reporting points

ET_HDR_DYNP: Table with production version screen data (used in TA PPEHDR02)

,,,,- PNGUID ( type PVS_PNGUID (Raw 16), Internal Number of iPPE Node)

***** DB tables

- PPEHDR (iPPE Access Object):

,,-> key = PPEGUID

- PPELNK (Connection Between PPEHDR and PPEOBJ):

,,-> key = PPEGUID, OBJCNT

- PPEOBJ (Objects for the iPPE Access Object):

,,-> key = OBJID, OBJCNT

,,,,==> join condition:

,,,,PPELNK - PPEGUID,, = PPEHDR - PPEGUID

,,,,PPEOBJ - OBJID,,,, = PPELNK - OBJID

,,,,PPEOBJ - OBJCNT,, ,,= PPELNK - OBJCNT

- PNODID (iPPE Node: Identification):

,,--> key = PNGUID (type PVS_PNGUID, Raw 16, Internal Number of iPPE Node)

,,,, PGUID = PNGUID in DB table PNODID

,,,, this is the GUID e.g. for a PPM routing header or access object

,,,,in PPC tables (e.g. //ppc_rpv1) this is the nodid

- /SAPAPO/TRPROD (Sources of Supply):

,,- NAME (type /SAPAPO/TR_NAME): in case of iPPE -> Production version

,, - TRPTYPE: Has value '3' in case of iPPE

,,- Connection to DB table PPEHDR is via field PPEGUID (type PVS_GUID (Raw 16))

********* Domain Values

Domain values of PPE_OBJTYPE (Object Type of the iPPE Header Object):

,,CMP,,Component

,,POS,,Variant

,,CON,,Concept

Domain values of PVS_OTYPE (iPPE Object Type (Node, Variant, Alternative)):

,,N,,Node

,,A,,Alternative

,,V,,Variant

,,R,,Relationship

Values of APPLOBJ_TYPE (see also definition of "ppet_applobj_type" in type group PPET)

,,CMP,,Product Structure

,,COL,,Color Scheme

,,ACT,,Process Structure

,,FLO,,Factory Layout

,,RES,,Production Resource

,,WTY,,Warranty Processing

,,SET,,Set Documentation

,,GEN,,Early Engineering

Notes

Further information

Parameters

ET_HDR_DYNP
ET_HEADER
ET_PPE
ET_RP_REL
ET_RP_SORT
IS_ORD_EXT
IV_LOCNO
IV_MATNR
IV_VEREXT

Exceptions

NO_LOCATION
NO_PRODUCT

Function Group

APO/SAPLFOT_TEST

BAL Application Log Documentation   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4602 Date: 20240419 Time: 034207     sap01-206 ( 49 ms )