Ansicht
Dokumentation

/SAPAPO/COLLECT_DATA_REM_HEUR - Collects Interface Data for REM Heuristics

/SAPAPO/COLLECT_DATA_REM_HEUR - Collects Interface Data for REM Heuristics

ROGBILLS - Synchronize billing plans   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

The function module collects the master- and transactions data necessary for the repetitive manufacturing heuristics.

The following Import parameter are transferred:

  • IV_START_TIME
  • Beginning of the time period, for which the heuristic run is executed.

  • IV_END_TIME
  • End of the time period, for which the heuristic run is executed.

  • IT_PEGAREA
  • Table with product- / location combinations, for which the heuristic run is executed.

  • IT_RESOURCES
  • Table with resources, for which the heuristic run is executed.

  • IT_LINES
  • Table with line networks, for which the heuristic run is executed.

  • IV_SIMID
  • GUID of simulation version

  • IV_SIMSESSION
  • GUID of simulation version

  • IS_HEUR_SETTINGS
  • Heuristic parameters

  • IV_AUTH
  • Determines whether a authorization check should be executed or not.

The environment is analyzed on the basis of the transferred resources table IT_RESOURCES. This means, that all products are derived, which can be produced from the specified resources. Subsequently the system checks to see whether these products can be produced using other resources than those contained within IT_RESOURCES. If this is the case, the environment will also be analyzed for these additional resources. The analysis is repeated, until the quantity of resources and products specified for planning has been reached.

When the function module for the table IT_PEGAREA has been transferred, the environment is analyzed analog to the procedure for IT_RESOURCES.

If the indicator IV_AUTH is set, the system checks, after the environment analysis for the found resources and products, whether authorization for changing exists. The objects for which this is not the case, are subsequently not included.

The resources and product-/ location combinations, which are determined by the environment analysis, are finally those, which are necessary for the REM heuristic master- and transaction data.

The data is transferred using the following Export parameters :

  • ET_RESOURCES
  • The tables of resources determined from the environmental analysis, for which the heuristic run is executed. The complete data from the master data is transferred for each resource

  • ET_PRODUCTS
  • Tables of product and location combinations determined from the environmental analysis for which the heuristic run is executed. As well as the key for each product and location combination, the product and location short texts are also transferred with all further information.

  • ET_PPM_PROD_RES
  • Contains the relevant information for REM heuristics from PPM's. The associated PPM's are read for all product and location combinations contained within ET_PRODUCTS. A line per activity and mode is transferred for each PPM.

  • ET_RTO_PROD_RES
  • Contains the information from the runtime object that is relevant for the REM heuristics. The corresponding runtime objects are read for all product and location combinations contained within ET_PRODUCTS. One row is transferred for each activity and mode.

  • ET_PPE_PROD_LIN
  • Contains the relevant information for REM Heuristics from iPPE's. The associated iPPE's are read for all product and location combinations contained within ET_PRODUCTS. A line with the capacity data of the resources for the associated line network is transferred for each iPPE

  • ET_PROD_ON_LINE
  • Contains summarized data from the tables ET_PPM_PROD_RES and ET_PPE_PROD_LIN.

  • Only one line per mode is transferred for each PPM. Displayed amongst others are: the number of the output operation (VORNR), the GUID of the output activity (ACTID), fixed time span for output operation (DUR), rate for output operation (RATE). The rate is calculated by dividing the variable time span of the output operation by the output quantity. The output quantity is considered here including the scrap factor maintained in the PPM.

  • For each iPPE a line is displayed for the output resource of the associated line: The rates given, are those maintained in the master data for the line resource. Material dependent rates are considered.

  • ET_IO_PT
  • Complete requirements-/stock list

  • ET_IO_REQMT
  • Requirements

  • ET_IO_REC_UNFIRMED
  • Non-fixed access

  • ET_IO_REC_FIRMED
  • Fixed access

  • ET_UNFIRMED_LOAD
  • Non-fixed resource occupancy; one line is displayed for each non-fixed order per activity

  • ET_FIRMED_LOAD
  • Fixed resource occupancy; one line is displayed for each fixed order per activity.

  • ET_RES_PERIODS_S
  • Shift period split

  • ET_RES_PERIODS_VAR
  • Variable period framework for resources. This can be a daily period split, a weekly period split, a monthly period split or a user specific period split defined in the heuristic parameters. The output of the period split is dependent upon those settings transferred in the IS_HEUR_SETTINGS-HEUR_REM structure.

  • ET_ACT_SHIFT
  • Shift dependent resource occupancy. Should an activity for an order stretch out over one or several shift boundaries, then for every shift a line with the start and the end of that activity will be displayed for that particular shift.

  • EV_START_TIME
  • Start of the time period, for which the heuristic run is to be executed. It differentiates from the input parameter IV_START_TIME in terms of the details. Orders cannot be created in the past. The earliest possible starting time EV_START_TIME is therefore the current system date plus two days. The parameter IV_START_TIME is therefore overrode as required.

  • EV_END_TIME
  • End of the time period for which the heuristic run is to be executed.

Example

Example of the environment analysis:

  • Resources: R1, R2, R3, R4

  • Products: P1, P2, P3, P4, P5

  • Product-resources assignment : R1: P1, P3; R2: P1, P2; R3: P2, P4; R4: P5

If the input table IT-Resources is only completed with R1, the environment analysis is executed as follows:

Firstly all products which can be produced on R1 are identified : P1 and P3. Then a check is carried out to determine which other resources can be used to produce P1 and P3: R2. P2 can also be produced from R2. P2 can also be produced using R3. P4 is also produced from R3. R4 and P5 do clearly not enter into the environment analysis.

The export tables therefore contain the following: ET_RESOURCES: R1, R2, R3; ET_PRODUCTS: P1, P2, P3, P4.

Example of the rates calculation:

In PPM for P1 the following data is maintained:

  • general entries output quantity 10 units, output operation: 10 , Output operation has 3 activities:

,,,,act1: Setup (fixed duration: 300 sec.), act2: Produce (fixed duration: 600 sec., variable duration: 80 sec.),

,,,,act3: Tear down (fixed duration: 100 sec.), Scrap factor: 20 %. Therefore the following is derived as a fixed proportion of the operation duration DUR = 300 + 600 + 100 [sec.] = 1000 [sec.]

For the rate: RATE = variable time / yield.

The yield results from the output quantities, reduced according to the scrap.

Therefore: yield = output quantity - scrap = output quantity * ( 1 - scrap factor) = 10 * (1 - 0.2) = 8 [units].

The resulting rate: RATE = 80 [sec.] / 8 [units] = 10 [sec./ unit]

Example of the shift period split

In the output table ET_RES_PERIODS_S a shift period split is transferred for every resource. The shift period split is located in the table "periods". Every row represents a working period, which is neither interrupted with a break nor the end of a shift.

  • Shift program with 3 shifts: 06.00-14.00, 14.00-22.00, 22.00-06.00 (Begin: 01.12.1999)

  • Additionally, there should be a break of 1 hour after three hours in every shift.

  • The following working periods result:

,, 06.00-09.00, 1. Shift

,,10.00-14.00, 1. Shift

,,,,14.00-17.00, 2. Shift

,,,,18.00-22.00, 2. Shift

,,,,22.00-01.00, 3. Shift

,,,,02.00-06.00, 3. Shift

  • The utilization of the resource amounts to 80 percent.

,,,,

The following rows are displayed:

Periods: START_STAMP END_STAMP START_DATE SHIFT_NO PERTYP PERTIME EFFTIME EFFICIENCY

1.Row: 19991201060000 19991201090000 19991201 1 S 10800 8640 80

2.Row: 19991201100000 19991201140000 19991201 1 S 14400 11520 80

3.Row: 19991201140000 19991201170000 19991201 2 S 10800 8640 80

and so on....

,,START_STAMP , END_STAMP and START_DATE,, denotes the start- and end time, or date of the ,,working period. PERTIME denotes the duration of the working phase, EFFICIENCY the resource utilization (in percent) and ,,EFFTIME the effective duration. Therefore EFFTIME = PERTIME * resource utilization (in percent).

Example of the daily period split

In the output table ET_RES_PERIODS_D a daily period split is transferred for every resource. The daily period split is located in the periods table. Each row represents one day.

START_STAMP denotes the start of the first shift on that particular day, and ENDSTAMP the end of the last shift. The current date is found in the START_DATE. In PERTIME, EFFICIENCY and EFFTIME the total duration of the working periods (breaks deducted), the resource utilization, and the effective duration are given analog to the shift period split.

The weekly and monthly period splits are set up analog to the daily period split.

Notes

Prerequisites for the sensible implementation of the module are:

  • that the products lie on a requirements planning level, that means that no dependent requirements can arise. Should products be found in the environment analysis, which lie on differing requirements planning levels, the module exits with an exception.
  • that the operation relevant to the planning is the output operation. With the calculation of the rate it is assumed, that the mode linkage over the resource is completed. Furthermore it is assumed when considering the scrap factor, that scrap is only relevant for one activity within the output operation, this being primarily "produce". Should a scrap factor also be maintained in the PPM in other activities or operations, these will not be correctly taken into account.

For those PPM's with several operations it is possible to determine the rate from the information contained within the table ET_PROD_LOC_RES.

Not taken into account:

  • Setups which are dependent upon a sequence
  • Characteristics
  • Relationships between operations / activities
  • Temporal validity of PPM's

Further information





Parameters

ET_ACT_SHIFT
ET_CIO_PT
ET_FIRMED_LOAD
ET_IO_PT
ET_IO_REC_FIRMED
ET_IO_REC_UNFIRMED
ET_IO_RQMT
ET_PPE_PROD_LIN
ET_PPE_PROD_RES
ET_PPM_PROD_RES
ET_PRODUCTS
ET_PROD_LINE
ET_RESOURCES
ET_RES_PERIODS_S
ET_RES_PERIODS_VAR
ET_RTO_PROD_RES
ET_UNFIRMED_LOAD
EV_END_TIME
EV_START_TIME
IS_HEUR_SETTINGS
IT_LINES
IT_PEGAREA
IT_RESOURCES
IV_AUTH
IV_END_TIME
IV_SIMID
IV_SIMSESSION
IV_START_TIME

Exceptions

NO_AUTHORITY
NO_PRODUCTION_VERSION
VARIOUS_MRP_LEVELS

Function Group

APO/SAPLPT_HEUR

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 15318 Date: 20240329 Time: 140703     sap01-206 ( 220 ms )