apo loader file document

Apo Loader

Before using Apo Loader you have to generate the sheets for the objects you want to work with.For the generation click on the button below, select the objects you want to use and follow the generation procedure.You can also generate the sheets manually by inserting emtpy sheets into the ApoLoader map and using the format option.

Apo Loader Documentation

Attention: If the sheets are already generated it isn't necessary to generate them again.

Generate Sheets

http://p46407.wdf.sap-ag.de:1080/bapi

Before using Apo Loader you have to generate the sheets for the objects you want to work with.For the generation click on the button below, select the objects you want to use and follow the generation procedure.You can also generate the sheets manually by inserting emtpy sheets into the ApoLoader map and using the format option.

If the sheets are already generated it isn't necessary to generate them again.

logical_system

logical_system

Description Logical System from which Message Originatesdata element/extended info bapiapologsys

-> documentation

char/ 10/

A1

bapi_locsrvaps_savemulti2

B1

bapi_locsrvaps_getlist2

A2

FUNCTIONALITY You can use this method to create and change locations. If a location already exists with the key specified, it is changed. However, if it does not yet exist, it is newly created. Note that the location can only be created if the external key ("Location", "Loctype") is also given. If you want to change locations that already exist, you can use the internal key ("LocationId" or "LocationInt", "Loctype") as well as the external key. In general, you can only create or change locations that exist in the business system group to which the logical system specified belongs ("LogicalSystem"). HINTS When you transfer communication methods ("LocationSmtp", "LocationFax", "LocationTel", and "LocationUri") you should note that a valid "LocationAddress" entry must always also be specified. Note: It is not yet possible to use the BAPI to change specific location data in a planning version other than the active version. The data provided in the "LocationVersion" parameter always applies to the active version. Ensure that you provide valid values for the different fields. There is no check for the value ranges of the fields. When this method is executed, no database locks are set and evaluated, since the interface has highest priority. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information

B2

FUNCTIONALITY You can use this method to read locations for certain selection criteria. HINTS You have the following options for selecting the locations. Combinations of alternatives are not possible and are ignored. Selection using location GUIDs "LocationGuids" Selection using RANGES tables: For this, the following combinations may be used: "LocationSelection" + "ModelSelection" (optional) + "BsgSelection" + (optional) + "LoctypeSelection" (optional) "LocationIntSelection" + "ModelSelection" (optional) + "BsgSelection" (optional) + LoctypeSelection" (optional) Selection using explicit keys: "LocationKey" "LocationIntKey" In addition to the three selection variants, you can use the "PlanningVersionSelection" parameter to restrict the planning versions for which data is returned in the "LocationVersion" parameter. If the parameter is empty, only planning-version-dependent data is returned for the active version. Note that the logical system must also be specified for all selection variants. If selection is carried out using internal keys ("LocationIntSelection", "LokationIntKey") or GUIDs ("LocationGuids"), the external keys are not filled in the return parameters. Only the internal keys are returned. If you want to determine the associated external key, you have to read using the internal key and business system group in the "LocationMapping" parameter. For selection using external keys ("LocationSelection", "LocationKeys"), both the internal and external key are always returned. Note also that this method can read data for locations from different business system groups. There is no restriction to the business system group to which the logical system specified belongs. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information Use internal selection

B4

The logical system identifies the sending system (client), from which the request originates. It is a logical system for ALE. Meaning of the logical system for BAPI interfaces in APO. Logical systems can be maintained in ALE Customizing.

B8

Checktable: /SAPAPO/SYSDIR Valuetable: TBDLS Conversion Exit: ALPHA

B9

10

B10

DEFINITION Logical system is a term from the ALE environment. In some BAPI interfaces it determines the business system group. Because every system group is a assigned to a logical system the system group can be determined accordingly. The logical system and the system group are used to carry out mapping to APO internal keys from external keys (for example, product numbers, order numbers from an OLTP system). If objects in an APO system should be addressed by their external numbers (which means that GUIDs are not used), the logical system (for example, for order numbers or special stock keys) or the system group (for example, products) is used. Note: Depending on the BAPI used, the system group or logical system specified for mapping the external key (for example, of an OLTP system) to APO internal keys can be controlled by explicitly specifying the external keys. Note the following when entering the logical system: At interfaces for orders: In the case of an external order number, (for example, 100) this order number is only unique in combination with a logical system, as the same order number can be transferred to the APO system from different external logical systems. That means you have to specify the logical system from which the order is transferred into the APO system. Note that this applies only to orders that have been created with external number assignment. For orders, the logical system is also used (with external number assignment) to determine which external system may need to be informed of an order change in SAP APO (using CIF or events). The Customizing settings are used to determine if the system is an SAP R/3 or non-SAP-R/3 system. If the incorrect logical system is entered or the Customizing settings are incorrect, this may mean that order changes in SAP APO are not transferred or transferred with errors. For example, this could be happen if the logical system entered is defined as R/3, although it is not an SAP R/3 system. In this case, APO would attempt to send changes to this system using CIF, but because the target system is not an SAP R/3 system, it cannot receive these function calls and errors occur. If the logical system of APO was entered, the APO system would attempt to send any changes to orders back to itself if this was set in Customizing. However, this is not possible and so the logical system of APO may not be used together with external number assignment. If you specify a product or a location in a BAPI you also have to specify the system group of these master data (usually the system from which the master data are tranferred to the APO system.) To determine the system group you can also use the logical system. This can be the case with GetList methods of orders if you select by orders for specific products. It is also important for some other fields (for example, SPEC_STOCK_IND + SPEC_STOCK_KEY) which logical system is given since this is also part of the key. General definition from ALE view

location_head

location_id location loctype location_int

Location GUID (Length 32) Location: External Location Identifier Location Type Locationbapi10002locid_32 /sapapo/loc_extlocno /sapapo/c_loctype /sapapo/locno

char/ 32/ char/ 20/ char/ 4/ char/ 20/

C4

MEANING Transfer parameter for general location data. HINTS The permitted values for the "Longitude" and "Latitude" fields (which represent GPS coordinates) should be filled as follows: DEGREEMINUTE/60+SECONDS/3600 Example: You want to map a longitude with the GPS coordinates 30 degrees, 10 minutes, 20 seconds. In this case, you fill the "Longitude" field with the value 30,10/60+20/3600 = 30,172222222. You use the "TpvsResUsage" field to specify which resource you want to use (no resource, time window resource, inbound/outbound handling resource). Here, you should ensure that the resources specified already exist in the system. In addition, all resources (except the time window resource) must be created on a location-dependent basis. That is, you must first create the location, then the resource, then enter the resource at the location. Dependent objects such as the "StorageResource" at the location object can be entered using either their internal or external key. If the relevant field for the business system group ("StorageResourceBsg") is empty, the name ("StorageResource") is interpreted as an internal name. However, if the field is filled, the name ("StorageResource") and the relevant business system group ("StorageResourceBsg") form the external key. DEFAULT

E6

1001 Production Plant 1002 Distribution Center 1005 Transportation Zone 1006 Stock Transfer Point 1007 Storage Location MRP Area 1010 Customer 1011 Vendor 1050 Subcontractor 1020 Transportation Service Provider 1030 Terminal 1031 Geographical Area 1040 Stores

C9

32

D9

20

E9

4

F9

20

C10

DEFINITION GUID definition GUIDs are usually created in the APO system. In some interfaces, a GUID can also be taken from an external system. In this case, the GUID must be generated using the specified algorithm (some programming languages provide their own APIs). It is not possible to generate the GUID again (for example, with user-defined characters). Display Format of the GUID: CHAR32 A 128 bit GUID corresponds to 16 Bytes. For CHAR32 display, each byte is displayed as two hexadecimal numbers. This results in 16 * 2 = 32 characters. The display is made using capital letters because this is the usual transfer format and is used in most interfaces. CHAR22 A 128 bit GUID corresponds to 16 Bytes. For CHAR22 display, each byte is converted into a CHAR22 character string using a special algorithm. The display contains lower case and capital letters. RAW16 Display using 16 Byte.

D10

DEFINITION Denotes a plant, a customer, or a vendor, for example, in the OLTP system.

E10

DEFINITION Key for the location type.

F10

DEFINITION Alphanumeric key uniquely identifying a location.

D11

BAPI10002LOCATIONHELP/LOCATION_EXT

F11

BAPI10002LOCATIONHELP/LOCATION_INT

global_location_number location_duns

Location: Global Location Number Location: DUNS+4 Number/sapapo/loc_gln /sapapo/loc_duns4

numc/ 13/ char/ 13/

G9

13

H9

13

longitude latitude time_zone

Longitude Specified in GPS Coordinates Latitude Specified in GPS Coordinates Time Zone/sapapo/loc_horizgps /sapapo/loc_vertigps tznzone

fltp/ 16/ fltp/ 16/ char/ 6/

K8

Valuetable: TTZZ

I9

22

J9

22

K9

6

K10

DEFINITION The time zone describes the location of an object in relation to its local time. The basic field assignments describe The time difference of the time zone in hours/minutes relative to the UTC The beginning and end of summer time On the basis of these field assignments, you do not need to use different time zones for summer and winder time, nor are these appropriate. It is possible to convert local times between the local time and a UTC time stamp using the ABAP command convert. The parameters are always the local time (date and time), the time zone, and the UTC time stamp.

priority edi_partner collaboration_partner business_partner

Priority of Location EDI Partner Number Location: Collaboration Partner Business Partner Number/sapapo/locprio /sapapo/loc_edipartner /sapapo/loc_clppaid bu_partner

int1/ 3/ char/ 10/ char/ 10/ char/ 10/

M8

Valuetable: EDPP1 Conversion Exit: ALPHA

O8

Valuetable: BUT000 Conversion Exit: ALPHA

L9

3

M9

10

N9

10

O9

10

L10

DEFINITION CTM: A control parameter used to assign a processing sequence to locations. The location priority is also used to set the processing sequence for location-dependent objects. TP/VS Indicates the location priority for a cost profile. Orders for locations with a certain priority receive the appropriate penalty costs for non-delivery or delayed delivery. USE Enter the value 1 for the highest priority. The higher the number entered, the lower the priority. If you do not enter a value, the system automatically assigns the value 0, giving the location the highest priority. Location priority is used in the area CTM.

N10

DEFINITION An independent entity in a collaboration process. You can assign more than one planner to a partner. DEPENDENCIES In the collaborative process, partners are responsible for completing prerequisites for certain activities. Prerequisites are expressed as alerts and statuses which are created in the planning book using advanced macros. EXAMPLE In the forecast consensus process, there could be 4 activities: Activity 1: enter forecast 1 Activity 2: enter forecast 2 Activity 3: enter forecast 3 Activity 4: create consensus foreacst based on figures in forecasts 1, 2and 3. A prerequisite for Activity 4 is the completion of activities 1, 2 and 3. As soon as the participants enter their forecast figures in the planning book, the activities are assigned a status, for example, Completed.

O10

DEFINITION Key identifying a business partner in the SAP system. The key is unique within a client.

quantity_indicator demand_consumption

Indicator for Calculation of Promotional Quantities Extended Forecast Consumption/sapapo/loc_prcind /sapapo/loc_decons

char/ 1/ int1/ 3/

P6

S Only Normal Sales Quantities Transmitted P Only Promotional Quantities Transmitted

Q6

0 Maximum Logic for Forecast Consumption 1 Standard Logic for Forecast Consumption

P9

1

Q9

1

P10

DEFINITION The business partner (operator of the location) calculates the forecast for the numbers of a promotion himself. The following values are possible: S: Only the requirements for the usual turnover quantities are made available by the business partner (turn = total forecast; promotion quantity = sales - total forecast). P: Only the requirements for the promotional quantities are made available by the business partner (basic turn = 0; promotion = sales). USE DEPENDENCIES EXAMPLE

Q10

DEFINITION In this field, you specify the logic for the forecast consumption at a customer location. Choose either the maximum or standard logic. USE This indicator controls the consumption of the forecast with the sales orders that the VMI customer receives from his customers. You can store these sales orders in the key figure 9ATSSALES. If you enter the value "1" in this field, the system uses the "standard" logic, to use the usual forecast consumption. For more information, refer to the section "Consumption in SAP APO" in the SAP APO documentation. If you enter "0" in this field (initial), the system uses the "maximum" logic. This logic is based on the maximum of the sales orders and the forecast. DEPENDENCIES If you use the standard logic, the parameters for the forecast consumption (e.g. consumption periods) are determined from the requirement strategy of the location product at the customer location. EXAMPLE

production_calendar warehouse_calendar shipping_calendar display_calendar

Production Calendar Calendar of a Warehouse Shipping Calendar PPDS Display Calendar/sapapo/loc_ppcal /sapapo/loc_stcal /sapapo/loc_sdcal /sapapo/shcal


R8

Valuetable: TTSTR

S8

Valuetable: TTSTR

T8

Valuetable: TTSTR

U8

Valuetable: TTSTR

R9

10

S9

10

T9

10

U9

10

R10

DEFINITION Is a planning calendar that is based on a factory calendar and is represented as a continuous time stream. USE The production calendar is used to schedule production activities. A production calendar valid for the entire production is assigned to a location. DEPENDENCIES Create a time stream for this calendar in Customizing: Choose Advanced Planner and Optimizer (APO) -> Master Data -> Calendar -> Maintain Planning Calendar (Time Stream). EXAMPLE

S10

DEFINITION A planning calendar that is based on a factory calendar and is represented as a continuous time stream. USE It is created for the scheduling of warehousing/storage activities. A warehouse calendar regulating the accessibility of a storage facility for stock putaway and removal purposes is assigned to a location. DEPENDENCIES Create a time stream for this calendar in Customizing: Choose Advanced Planner and Optimizer (APO) -> Master Data -> Calendar -> Maintain Planning Calendar (Time Stream). EXAMPLE

T10

DEFINITION Is a planning calendar (time stream) that is based on a factory calendar and is represented as a continuous time stream. USE The shipping calendar is used to schedule shipping activities. A shipping calendar valid for the entire shipping function is assigned to a location. DEPENDENCIES Create a time stream for this calendar in Customizing: Choose Advanced Planner and Optimizer (APO) -> Master Data -> Calendar -> Maintain Planning Calendar (Time Stream). EXAMPLE

U10

DEFINITION USE In the display calendar, you can determine the display of periodic views in the product planning table for Production Planning and Detailed Scheduling (PP/DS). In the Daily Buckets view, non-workdays such as weekends or public holidays, are not displayed for example. In the display calendar, you can determine the non-workdays for the relevant location. If the display calendar has not been maintained, PP/DS uses the production calendar. DEPENDENCIES EXAMPLE

receiving_calendar purchasing_block_flag stock_cat_grp

Receiving Calendar Centrally Imposed Purchasing Block Category Group for Stocks/sapapo/loc_rccal /sapapo/sperm /sapapo/loc_stocg

char/ 10/ char/ 1/ char/ 3/

W6

Blank . Radio button X Selection

V8

Valuetable: TTSTR

V9

10

W9

1

X9

3

V10

DEFINITION Planning calendar (time stream) that is based on a factory calendar and represented as a continuous time stream. USE The receiving calendar is created to schedule goods receiving activities. A receipt calendar valid for the entire goods receipt process is assigned to a location. . DEPENDENCIES Create the time stream for this calendar in Customizing. For more information, refer to the Implementation Guide (IMG) under Advanced Planner and Optimizer (APO) -> Master Data -> Calendar -> Maintain Planning Calendar (Time Stream).

X10

DEFINITION Covers category groups containing categories (such as stock categories and production categories) that specify which receipt and stock quantities comprise the ATD quantity. USE A category is assigned to each receipt element. These categories can be consolidated to form category groups.

atd_issue_cat_grp atd_receipt_cat_grp

Category Group for ATD Quantity (Issues) Category Group for ATD Quantity (Receipts)/sapapo/loc_atddm /sapapo/loc_atdsp

char/ 3/ char/ 3/

Y9

3

Z9

3

Y10

DEFINITION USE This field is relevant to Deployment in Supply Network Planning (SNP). With the category group for the ATD issue, you specify which order categories contribute to the reduction of the Available-to-Deploy Quantity (ATD quantity) (for example, BM = sales orders). DEPENDENCIES You can specify this field in both the location product master and the location master. When Deployment is carried out, the system first checks whether the category group has been specified for the location product. If not, the system checks the entry at location level. If no category group has been defined for the location either, the system uses the standard category group ATI. You define the category group in Customizing for SNP under Maintain Category Groups.

Z10

DEFINITION Covers category groups containing USE This field is relevant to Deployment in Supply Network Planning (SNP). With the category group for the ATD receipt, you specify which order categories contribute to the increase of the Available-to-Deploy- Quantity (ATD quantity) (for example, EE = SNP planned orders). DEPENDENCIES You can specify this field in both the location product master and the location master. When Deployment is carried out, the system first checks whether the category group has been specified for the location product. If not, the system checks the entry at location level. If no category group has been defined for the location either, the system uses the standard category group ATR. You define the category group in Customizing for SNP under Maintain Category Groups.

prohibit_push_flag vehicle_location_comp_flag tp_create_lead_time

Push not Allowed Compatibility: Means of Transport/Location Shipment Creation Lead Time/sapapo/loc_snpdplpudis /sapapo/comp_flag /sapapo/trpcr_time

char/ 1/ char/ 1/ quan/ 13/ 3

AA6

X Flag set; event has occurred Flag not set

AB6

A All means of transport I Incompatible means of transport C Compatible means of transport

AC8

Reference Table: BAPI10002LOC2O Reference Field: TP_CREATE_LEAD_TIME_UOM

AA9

1

AB9

1

AC9

17

AA10

DEFINITION Indicates that the location is excluded from push deployment. If this indicator is set, the available supply is only distributed in accordance with the daily requirement of the location. USE DEPENDENCIES The indicator can only be set for the active version. EXAMPLE A location may be excluded from push deployment if its storage capacity is limited, for example. It then receives only the quantity that covers its daily requirement.

AB10

DEFINITION Specifies which entries in the table for the IMG activity Maintain Compatibility of Location/Means of Transport are taken into account. USE You have the following selection options: All Means of Transport, irrespective of compatibility Compatible Means of Transport Incompatible Means of Transport Not choosing a value is equivalent to choosing All Means of Transport. In this case, the system assumes that each means of transport maintained on the associated transportation lanes for this location is compatible, irrespective of the table entries maintained in the IMG activity Maintain Compatibility of Location/Means of Transport. DEPENDENCIES You define the assignment denoting whether or not a means of transport is compatible with a location in Customizing for APO under Transportation Planning/Vehicle Scheduling (TP/VS) -> Basic Settings -> Maintain Compatibility of Location/Means of Transport . You can go direct to this IMG activity by clicking the button to the right of this field. EXAMPLE Example 1 If you have maintained 100 means of transport, two of which are to be compatible with the location, maintain an entry for each of these two means of transport in the IMG activity Maintain Compatibility of Location/Means of Transport and set the two entries to Compatible . Choose Compatible Means of Transport in this field. Example 2 If you have maintained 100 means of transport, two of which are to be incompatible with the location, maintain an entry for each of these two means of transport in the IMG activity Maintain Compatibility of Location/Means of Transport and set the two entries to Incompatible. Choose Incompatible Means of Transport in this field.

AC10

DEFINITION Indicates the duration required for the shipment to be transferred from APO to the OLTP system, so that the appropriate shipment documents can be created before loading begins.

tp_create_lead_time_uom tp_create_lead_time_uom_iso pick_lead_time

Time Unit ISO code for unit of measurement Picking Lead Time/sapapo/trpcr_time_unit isocd_unit /sapapo/com_time

unit/ 3/ char/ 3/ quan/ 13/ 3

AD8

Valuetable: T006 Conversion Exit: CUNIT

AE8

Valuetable: T006I

AF8

Reference Table: BAPI10002LOC2O Reference Field: PICK_LEAD_TIME_UOM

AD9

3

AE9

3

AF9

17

AE10

DEFINITION ISO code for measurement units. An ISO code can be assigned to several internal measurement units. USE The ISO code is important for EDI. It is used to convert the internal SAP measurement units into standard measurement units. Data exchange via EDI requires internal measurement units to be converted into standard measurement units. A list of the current internationally agreed ISO codes can be ordered from the UN commission responsible (WP.4 Trade Facilitation Recommendations, Recommendation 20): UN Economic Commission for Europe Information Office Palais des Nations 1211 Geneva Switzerland phone: +4122 917 2893 fax: +4122 917 0036 e-mail: [email protected] or it can be consulted directly via internet: http://www.unece.org/trade/facil/tf_home.htm For additional information see OSS note 69063. WHAT_TO_DO EXAMPLES DEPENDENCIES

AF10

DEFINITION Indicates the time required to make an order from the APO system available before the material availability date of the OLTP system, so that picking can take place in the OLTP system based on the corresponding deliveries.

pick_lead_time_uom pick_lead_time_uom_iso first_visit_flag last_visit_flag

Time Unit ISO code for unit of measurement Visit First Visit Last/sapapo/com_time_unit isocd_unit /sapapo/fvisit /sapapo/lvisit

unit/ 3/ char/ 3/ char/ 1/ char/ 1/

AI6

X Yes No

AJ6

X Yes No

AG8


AH8

Valuetable: T006I

AG9

3

AH9

3

AI9

1

AJ9

1

AH10


AI10

DEFINITION Set this indicator if you want this location to be visited first during a tour. This information is important for the vehicle scheduling optimization run.

AJ10

DEFINITION Set this indicator if you want the location to be visited last during a tour. This information is important for the vehicle scheduling optimization run.

std_carrier_access_code continous_move_flag

Standard Carrier Alpha Code Continuous Move/sapapo/loc_scacd /sapapo/loc_contmove

char/ 4/ char/ 1/

AL6

X Yes No

AK9

4

AL9

1

AK10

DEFINITION Identifies the transportation service provider (TSP). USE Assign such a code as the external TSP ID. This code is independent of the data maintained in the system.

AL10

DEFINITION Indicates whether the transportation service provider directly accepts a complete new shipment upon completion of the original transportation at the point of destination (continuous move). USE Set this indicator if a continuous move is involved.

max_break_continous_move procedure

Maximum Duration of Break During Continuous Move Allocations: Product Allocation Procedure/sapapo/loc_durat /sapapo/loc_kosch

dec/ 11/ 0 char/ 18/

AM8

Conversion Exit: TSTRN

AM9

10

AN9

18

AM10

DEFINITION States the length of time that a carrier is prepared to wait between two transportations during a continuous move. DEPENDENCIES To be able to maintain a time buffer, the Continuous Move indicator must be set.

AN10

DEFINITION The product allocation procedure stipulates how a product of which only a limited quantity is available is to be apportioned among sales orders. The product allocation schema can also be location-dependent (selection see location-dependent product allocation procedure) USE You enter the allocation procedure on the APO data screen of the APO product master record or in a sequence of product allocation procedures. DEPENDENCIES In addition, various settings in Customizing determine how the allocation is carried out: Several allocation steps can be defined in a product allocation procedure You assign an allocation group to the allocation step. The allocation group defines the criteria according to which an allocation is selected in the availability check. The consumption period determines the periods of the product allocation time series around the check date whose free allocation quantity may be used for the confirmation calculation. The consumption period is defined per allocation group. In the product allocation control of an allocation step, you can assign several product allocation objects. Each of these objects is valid for an interval. The product allocation objects represent the reason for the allocation. The allocation object is the first characteristic in the allocation group. If the allocation object is changed, a different allocation time series is used for the relevant interval in the check.

tsp_performance loading_res_inbound

Transportation Service Provider Performance (in %) Loading Resource (Inbound)/sapapo/loc_performance /sapapo/loc_tpresname_inb

dec/ 4/ 1 char/ 40/

AO9

5

AP9

40

AO10

DEFINITION Describes the quality level of a transportation service provider in the form of a percentage. USE Specify a percentage for the performance. The higher the figure, the better your quality rating.

AP10

DEFINITION Identifies the resource that is used to load or unload a vehicle during the inbound delivery process. DEPENDENCIES You must have already maintained a single or multi resource of the resource type H (handling unit) and assigned it to the location in the resource master. You must also have assigned this resource to the model in which you are working. The component Transportation Planning/ Vehicle Scheduling (TP/VS) can only process non-dimenstional capacities for loading resources. For this reason, you must define the capacity of the loading resource as non-dimensional in the resource master.

loading_res_inbound_bsg loading_res_outbound loading_res_outbound_bsg

Business System Group Loading Resource (Outbound) Business System Group/sapapo/logqs /sapapo/loc_tpresname_out /sapapo/logqs


AQ8

Valuetable: /SAPAPO/SYSLST

AS8


AQ9

8

AR9

40

AS9

8

AQ10

DEFINITION The business system group integrates different physical systems into one higher-level logical unit. USE We recommend that you assign the APO System to the same business system group (BSG) to which the logical system or the R/3 instances, which contain the master data server, belong. Only after you have made such an assignment, can you maintain the master data in the APO System. DEPENDENCIES Maintain system group Assign logical system

AR10

DEFINITION Identifies the resource that is used to load or unload a vehicle during the outbound delivery process. DEPENDENCIES You must have already maintained a single or multi resource of the resource type H (handling unit) and assigned it to the location in the resource master. You must also have assigned this resource to the model in which you are working. The component Transportation Planning/ Vehicle Scheduling (TP/VS) can only process non-dimenstional capacities for loading resources. For this reason, you must define the capacity of the loading resource as non-dimensional in the resource master.

AS10


time_res_inbound time_res_inbound_bsg time_res_outbound

Opening Times of Location (Inbound) Business System Group Opening Times of Location (Outbound)/sapapo/loc_tresname_inb /sapapo/logqs /sapapo/loc_tresname_out


AU8


AT9

40

AU9

8

AV9

40

AT10

DEFINITION Indicates the resource for which the opening times for inbound delivery have been maintained for this location USE Use this resource for Vehicle Scheduling. The resource may not be a bucket resource or a mixed resource. We recommend using a calendar resource. You maintain the opening times via a resource in the resource master. Via the break times of the resource, you specify when access to the location is not possible. Use the Resource button to branch directly to the resource master. There you can display or change the data maintained for an existing resource. To create a resource, choose Master Data -> Resource in the APO menu. Note: A resource can be assigned to different numbers of locations. For this reason, note that when you change the times of a resource, the times will be changed for all related locations. If the same resource is to be used for the opening times for inbound and outbound, it must be maintained at both points.

AU10


AV10

DEFINITION Indicates the resource for which the opening times for outbound delivery have been maintained for this location USE Use this resource for Vehicle Scheduling. The resource may not be a bucket resource or a mixed resource. We recommend using a calendar resource. You maintain the opening times via a resource in the resource master. Via the break times of the resource, you specify when access to the location is not possible. Use the Resource button to branch directly to the resource master. There you can display or change the data maintained for an existing resource. To create a resource, choose Master Data -> Resource in the APO menu. Note: A resource can be assigned to different numbers of locations. For this reason, note that when you change the times of a resource, the times will be changed for all related locations. If the same resource is to be used for the opening times for inbound and outbound, it must be maintained at both points.

time_res_outbound_bsg tpvs_res_usage

Business System Group Ind: Handling Resources/Time Frame Resource/None/sapapo/logqs /sapapo/resflag

char/ 8/ char/ 1/

AX6

0 No handling resource 1 Time frame resource 2 Inbound/outbound handling resource

AW8


AW9

8

AX9

1

AW10


handling_res_inbound handling_res_inbound_bsg handling_res_outbound

Inbound Handling Resource Business System Group Outbound Handling Resource/sapapo/loc_hresname_inb /sapapo/logqs /sapapo/loc_hresname_out


AZ8


AY9

40

AZ9

8

BA9

40

AZ10


handling_res_outbound_bsg storage_resource storage_resource_bsg business_event

Business System Group Storage Resource Business System Group Business Event/sapapo/logqs /sapapo/loc_stresname /sapapo/logqs /sapapo/loc_prreg


BB8


BD8


BB9

8

BC9

40

BD9

8

BE9

2

BB10


BC10

DEFINITION Combines the functions of a storage facility (e.g. inventory management) with those of a resource (e.g. capacity planning). Storage resources link a location with a resource. This resource may be subject to temporal and quantity-based restrictions. USE You must have maintained a resource with the resource category S (storage facility) in the resource master.

BD10


BE10

DEFINITION A selection of defined operations within an enterprise's working routine. The selected business event triggers the ATP check. Beispiel Sale, receipt of order, shipment.

delivery_priority attribute_1 attribute_2 attribute_3

Location: Delivery Priority Character field of length 40 30 Characters Char 20/sapapo/loc_lprio char40 char30 char20

numc/ 2/ char/ 40/ char/ 30/ char/ 20/

BF9

2

BG9

40

BH9

30

BI9

20

attribute_4 attribute_5

Character Field Length = 10 Character Field Length = 10char10 char10

char/ 10/ char/ 10/

BJ9

10

BK9

10

subcontractor_plant subcontractor_plant_bsg

LOC: Ext. Name of Plant/DC/MRP Area Belonging to Subcontr. Business System Group/sapapo/subcon_plant_extlocno /sapapo/logqs

char/ 20/ char/ 8/

BM8


BL9

20

BM9

8

BM10


subcontractor_supplier subcontractor_supplier_bsg

LOC: External Name of Vendor Belonging to Subcontractor Business System Group/sapapo/subcon_suppl_extlocno /sapapo/logqs

char/ 20/ char/ 8/

BO8


BN9

20

BO9

8

BO10


promotion_upsizing promotion_downsizing

LOC: Upsizing in Case of Promotion LOC: Downsizing in Case of Promotion/sapapo/loc_promup /sapapo/loc_promdown

char/ 1/ char/ 1/

BP6

Upsizing Before Baseline A Upsizing After Baseline N No Upsizing with Promotions

BQ6

Downsizing after Baseline B Downsizing before Baseline N No Downsizing with Promotions

BP9

1

BQ9

1

order_processing_time time_series_profile base_profile

LOC: VMI Order Processing Time Time Series Profile (F&R) Base Profile for F&R/sapapo/loc_optime /sapapo/loc_prots /sapapo/loc_probase

dec/ 11/ 0 char/ 10/ char/ 10/

BR8


BR9

10

BS9

10

BT9

10

ord_qty_opt_profile

Name of Profile for Order Quantity Optimization (F&R)/sapapo/loc_prooqo

char/ 10/

BU9

10

round_up_cost_multiplier

Cost Multiplier for Rounding Up Promotion Quantities/sapapo/loc_costmultupprom

dec/ 13/ 3

BV9

17

round_down_cost_multiplier nielsen_code

Cost Multiplier for Rounding Down Promotion Quantities Nielsen Code/sapapo/loc_costmultdownprom /sapapo/loc_nielsen

dec/ 13/ 3 char/ 3/

BW9

17

BX9

3

location_text

location_id location loctype location_int langu

Location GUID (Length 32) External Location ID Location Type Location Language Keybapi10002locid_32 /sapapo/ext_locno /sapapo/c_loctype /sapapo/locno spras

char/ 32/ char/ 20/ char/ 4/ char/ 20/ lang/ 1/

BY4

MEANING Transfer parameter for language-dependent short texts. RANGE DEFAULT

CA6


CC8

Valuetable: T002 Conversion Exit: ISOLA

BY9

32

BZ9

20

CA9

4

CB9

20

CC9

2

BY10


BZ10

DEFINITION Denotes a plant, customer, supplier, and so on, in the OLTP system.

CA10


CB10


CC10

DEFINITION The language key designates the language in which you: Display texts Enter texts Print documents.

BZ11


CB11


location_address

langu_iso loc_descr location_id

Language according to ISO 639 Location Description Location GUID (Length 32)laiso /sapapo/c_loc_descr40 bapi10002locid_32


CF4

MEANING Transfer parameter for general address data. RANGE DEFAULT

CD9

2

CE9

40

CF9

32

CE10

DEFINITION Describes a location.

CF10


location loctype location_int title name name_2

External Location ID Location Type Location Form-of-Address Key Name 1 Name 2/sapapo/ext_locno /sapapo/c_loctype /sapapo/locno ad_title ad_name1 ad_name2

char/ 20/ char/ 4/ char/ 20/ char/ 4/ char/ 40/ char/ 40/

CH6


CJ8

Valuetable: TSAD3

CG9

20

CH9

4

CI9

20

CJ9

4

CK9

40

CL9

40

CG10


CH10


CI10


CK10

DEFINITION Address component: Name of an address

CG11


CI11


name_3 name_4 c_o_name city district city_no

Name 3 Name 4 c/o name City District City code for city/street filead_name3 ad_name4 ad_name_co ad_city1 ad_city2 ad_citynum


CR8

Valuetable: ADRCITY Conversion Exit: ALPHA

CM9

40

CN9

40

CO9

40

CP9

40

CQ9

40

CR9

12

CP10

DEFINITION City name as part of the address. The city name is saved redundantly in another database field in upper- case letters, for search help. If the Postal regional structure ('city file') is active, the city name is checked against the Cities defined in the regional structure.

CQ10

DEFINITION City or District supplement VERWENDUNG In some countries, this entry is appended with a hyphen to the city name by the automatic address formatting, other countries, it is output on a line of its own or (e.g. in the USA) not printed. See the examples in the Address Layout Key documentation.

distrct_no chckstatus regiogroup postl_cod1

District code for City and Street file City file test status Regional structure grouping City postal codead_citypnm ad_checkst regiogroup ad_pstcd1


CT6

Not checked C checked against city index D differs from city index

CS8

Valuetable: ADRCITYPRT Conversion Exit: ALPHA

CU8

Valuetable: ADRREGGRP

CS9

8

CT9

1

CU9

8

CV9

10

CU10

DEFINITION Regional structure grouping combines all elements of the regional structure (cities, streets, street sections). It is used, for example, for clerk determination.

CV10

DEFINITION Postal code as part of the address USE If different postal codes are maintained for the PO Box and Street address of an address, this field contains the Street address postal code.

postl_cod2 postl_cod3

PO Box postal code Company postal code (for large customers)ad_pstcd2 ad_pstcd3

char/ 10/ char/ 10/

CW9

10

CX9

10

CW10

DEFINITION Postal code that is required for a unique assignment of the PO box. USE This field is used for countries where a different postal code applies to mail that is sent to the PO box rather than to the street address of a particular business partner. Postal codes for group major customers also have to be entered in the field for the PO box postal code since individual customers with a shared postal code for group major customers are differentiated by means of the PO box. Postal codes for major customers (= company postal codes), however, are assigned to one customer only and have to be entered in the field 'Company Postal Code'.

CX10

DEFINITION Postal code that is assigned directly to one company (= company postal code = major customer postal code). USE This field is used for countries where major companies are assigned their own postal code by the national post office. This postal code has to be entered in the field "Company Postal Code". Postal codes for group major customers, however, have to be entered in the field "PO Box Postal Code", since individual customers with a shared postal code for group major customers are differentiated by means of their PO box.

pcode1_ext pcode2_ext

City postal code extension, e.g. ZIP+4+2 code PO Box postal code extension, e.g. ZIP+4+2 codead_pst1xt ad_pst2xt

char/ 10/ char/ 10/

CY9

10

CZ9

10

CY10

DEFINITION Postal code extension in an address. This field is not yet considered in dialog or when an address is printed. This field is not defined for the +4 extension of the US postal code (ZIP+4). The whole US postal code (ZIP+4) is maintained with the format 12345-6789 in the Postal code field, instead.

CZ10

DEFINITION Postal code extension in an address. This field is not yet considered in dialog or when an address is printed. This field is not defined for the +4 extension of the US postal code (ZIP+4). The whole US postal code (ZIP+4) is maintained in the format 12345-6789 in the Postal code field, instead.

pcode3_ext po_box po_w_o_no

Major customer postal code extension, e.g. ZIP+4+2 code PO Box Flag: PO Box without numberad_pst3xt ad_pobx ad_pobxnum


DC6

X Yes No

DA9

10

DB9

10

DC9

1

DA10

DEFINITION Postal code extension in an address. This field is not yet considered in dialog or when an address is printed. This field is not defined for the +4 extension of the US postal code (ZIP+4). The whole US postal code (ZIP+4) is maintained in the format 12345-6789 in the Postal code field, instead.

DB10

DEFINITION PO Box number as part of an address. Only enter the PO Box number in this field. The text "PO Box" is provided in the recipient language by the system when you print the address. When you print an address, the "Street address" and the "PO Box address" are distinguished. The print program determines which of them has priority if both are maintained in an address record. Besides the PO Box number, the PO Box address uses the following fields: PO Box postal code, if specified (otherwise the normal postal code) PO Box city, if specified (otherwise the normal city) PO Box region, if specified (otherwise the normal region) PO Box country, if specified (otherwise the normal country) If the address is a "PO Box" (without a number), do not fill the "PO Box" field. Select the "PO Box w/o Number" indicator instead. You can also enter a company postal code for organizational addresses, instead of a PO Box. A separate field is predefined for this entry. HINTS For general information and examples about address formatting, see the documentation on the Address Structure Key.

po_box_cit pboxcit_no po_box_reg

PO Box city City PO box code (City file) Region for PO Box (Country, State, Province, ...)ad_pobxloc ad_cit2num ad_pobxreg


DE8


DF8

Valuetable: T005S

DD9

40

DE9

12

DF9

3

DD10

DEFINITION Different city for the PO Box as an address component. USE The PO Box city can be entered here if it is different from the address city. If the address is only a PO Box address, enter the city in the normal city field. WHAT_TO_DO If the address contains two different city names for the address and the PO Box address, use this field. EXAMPLES DEPENDENCIES

pobox_ctry po_ctryiso deliv_dis

PO box country Country ISO code Post delivery districtad_pobxcty intca ad_pstlar


DG8

Valuetable: T005

DG9

3

DH9

2

DI9

15

DH10

DEFINITION International standardized country key in accordance with ISO 3166. USE The entry is used in countries of the European Community to check the VAT registration number (VAT reg.no.). You can store the VAT registration number in the master record of a customer or vendor, or for the company code. The ISO code is used as the country key when exchanging information via EDI. You must therefore specify the ISO code for each country in this field if you use EDI. The ISO code also controls which additional specifications are relevant for a company code. You can always only enter the additional details which are relevant for the company code country or for all countries. The assignment to the country takes place via the ISO code. WHAT_TO_DO Enter the ISO code for each country. This is of particular importance if the country belongs to the European Community if you exchange information via EDI if company-code specific additional specifications are to be limited by country.

DI10

DEFINITION This field is not yet used.

transpzone street street_no

Transportation zone to or from which the goods are delivered Street Street code for city/street filelzone ad_street ad_strnum


DJ8

Valuetable: TZONE

DL8

Valuetable: ADRSTREET Conversion Exit: ALPHA

DJ9

10

DK9

60

DL9

12

DJ10

DEFINITION Sales and distribution: Regional zone of Goods recipient. Purchasing: Regional zone of supplier. USE You can define regional zones to suit the requirements of your own business and country. Sales and distribution the system automatically proposes a suitable route by using the transportation zone of the goods recipient in combination with other information about the delivery, such as the Countries of origin and destination Shipping conditions Transportation group EXAMPLE In the USA, for example, you can define regional zones to correspond to the US postal zip codes.

DK10

DEFINITION Street name as part of the address. The street name is saved, redundantly in upper case in another database field, for search help purposes. There are other fields for address parts which can be printed above or below the street. See Print the Street address. HINTS The house number and other supplements are usually maintained in their own fields. See Formatting the Street line.

str_abbr house_no house_no2

Abbreviation of street name (e.g in Spain) House Number House number supplementad_strabbr ad_hsnm1 ad_hsnm2


DM8

Valuetable: ADRSTRTYPE

DM9

2

DN9

10

DO9

10

DN10

DEFINITION House number as part of an address. It is printed in the Street line. Other supplementary street information can be entered in the House number supplement or one of the Street2, Street3, Street4 or Street5 fields. See Print the Street address. A house number (e.g. 117) or a house number with supplement (e.g. 117a), or a house number range (e.g. 16-20), can be maintained in this field.

DO10

DEFINITION House number supplement as part of an address, e.g. App. 17 or Suite 600. It is printed in the Street line. Further Street supplements can be put in one of the fields Street2, Street3, Street4 or Street5. EXAMPLES See Print the Street address.

house_no3 str_suppl1 str_suppl2 str_suppl3 locatn building

House number range Street 2 Street 3 Street 4 Street 5 Building (Number or Code)ad_hsnm3 ad_strspp1 ad_strspp2 ad_strspp3 ad_lctn ad_bldng


DP9

10

DQ9

40

DR9

40

DS9

40

DT9

40

DU9

20

DP10

DEFINITION Not currently used.

DR10

DEFINITION Additional address field which is printed above the Street line. The Street address contains two lines above the street and two lines below the street. See Print the Street address.

DS10

DEFINITION Additional address field which is printed below the Street line. The Street address contains two lines above the street and two lines below the street. See Print the Street address.

DT10

DEFINITION Additional address field which is printed under the Street line. The Street address has two lines above the street and two lines below the steet. See Print the Street address.

DU10

DEFINITION Number or abbreviation of a building in an address. This field is not used when the address is printed. The name of a building such as "Empire State Building", which is also to appear in the printout of the address, must be stored above or below the street in one of the fields Street2, Street3, Street4 or Street5, depending on its position. See Print the Street address.

floor room_no country countryiso langu

Floor in building Room or Appartment Number Country Key Country ISO code Language Keyad_floor ad_roomnum land1 intca spras

char/ 10/ char/ 10/ char/ 3/ char/ 2/ lang/ 1/

DX8

Valuetable: T005

DZ8


DV9

10

DW9

10

DX9

3

DY9

2

DZ9

2

DV10

DEFINITION Floor of the building as more exact specification of an address. This field is not printed in the address. Floors which should be printed must be in the field house number supplement or in one of the fields Street2, Street3, Street4 or Street5 depending on the desired position. See Print the Street address.

DW10

DEFINITION Appartment or room number in an a ddress. This field is not printed. Entries which are to be printed must in the house number supplement field or in one of the Street2, Street3, Street4 or Street5 fields, depending on the desired position. See Print the Street address.

DX10

DEFINITION The country key contains information which the system uses to check entries such as the length of the postal code or bank account number. The two-character ISO code in accordance with ISO 3166, which is delivered by SAP as a default, is usually used. It could also be the vehicle license plate country-code or a typical country key, for example, in Germany the Federal statistics office key. The country keys are determined at system installation in the global settings. Since the country key does not have to correspond to the ISO code in all installations, programs that differ according to certain values of the country key cannot query the country key T005-LAND1, but have to program based on the ISO code T005 INTCA.

DY10


DZ10

DEFINITION The language key designates the language in which you: Display texts Enter texts Print documents.

langu_iso region sort1 sort2

Language according to ISO 639 Region (State, Province, County) Search Term 1 Search Term 2laiso regio ad_sort1 ad_sort2


EB8

Valuetable: T005S

EA9

2

EB9

3

EC9

20

ED9

20

EB10

DEFINITION In some countries, the region forms part of the address. The meaning depends on the country. The automatic address formatting function prints the region in addresses in the USA, Canada, Italy, Brazil or Australia, and the county in Great Britain. For more information, see the examples in the documentation on the Address Layout Key. EXAMPLES Meaning of the regional code in ... Australia -> Province Brazil -> State Canada -> Province Germany -> State Great Britain -> County Italy -> Province Japan -> Prefecture Switzerland -> Canton USA -> State

EC10

DEFINITION Short description for a search help. This field contains only upper-case letters. All entries are automatically converted to upper-case letters. There are two, independent, search term fields. WHAT_TO_DO You can determine your own search criteria. EXAMPLE It could be e.g. the significant part of the name or an organizational assignment code. Maintain, e.g. 'Hurst' as first search zerm for the company "Carl Hurst, Sons & Co. Ltd. plc". As second search term, maintain e.g. the name abbreviation used in your company, to find your data more easily later.

ED10

DEFINITION Short description for a search help This field contains only upper-case letters. All entries are automatically converted to upper-case letters. There are two, independent, search term fields. WHAT_TO_DO You can determine your own search criteria. EXAMPLE It could be e.g. the significant part of the name or an organizational assignment code. Maintain, e.g. 'Hurst' as first search zerm for the company "Carl Hurst, Sons & Co. Ltd. plc". As second search term, maintain e.g. the name abbreviation used in your company, to find your data more easily later.

extens_1 extens_2

Extension (only for data conversion) (e.g. data line) Extension (only for data conversion) (e.g. telebox)ad_extens1 ad_extens2

char/ 40/ char/ 40/

EE9

40

EF9

40

time_zone taxjurcode address_id

Address time zone Tax Jurisdiction Code Physical address IDad_tzone ad_txjcd ad_addr_id


EG8

Valuetable: TTZZ

EI8

Conversion Exit: ALPHA

EG9

6

EH9

15

EI9

10

EG10

DEFINITION Time zone as part of an address. The time zone is automatically determined by the system in address maintenance if time zone Customizing is maintained. It depends on the country and the region. (Region means state, province or county, depending on the country) The automatic determination is only made if there is no value in the time zone field.

EH10

DEFINITION Specifies the tax authority to which taxes must be paid. It is always the city to which the goods were delivered. USE The tax location is used for calculating tax rates in the USA. The tax location can be determined using the SAP regional structure or an external tool. The external tool takes precedence when determining the Tax Jurisdiction Code. WHAT_TO_DO EXAMPLES DEPENDENCIES

langu_cr langucriso

Address record creation original language Language according to ISO 639ad_langucr laiso

lang/ 1/ char/ 2/

EJ8


EJ9

2

EK9

2

EJ10

DEFINITION This field gives the logon language with which the address record has been created. This records in which language environment the search fields have been filled in upper case (for example, MC_STREET) using the language-dependent translate command. This can also be used to compare the logon language with the creation language when the address is changed and to prevent inconsistencies when updating the search fields named above. The field is automatically filled by the system when creating an address record.

comm_type home_city

Communication Method (Key) (Business Address Services) City (different from postal city)ad_comm ad_city3

char/ 3/ char/ 40/

EL8

Valuetable: TSAC

EL9

3

EM9

40

EL10

DEFINITION Communication method with which you can exchange documents and messages with a business partner. In Business Address Services, you can specify a standard communication method that can be used by programs to determine the means of communication for sending messages. EXAMPLE One business partner wants all messages by fax, another by e-mail. HINTS The application context can restrict the possible methods of communication. For example, invitations should perhaps only be sent by post because of enclosures, whereas minutes can be sent by post, fax or e-mail. Communication strategies can be defined for this purpose and applied in application contexts.

homecityno dont_use_s dont_use_p

Different city for city/street file Street Address Undeliverable Flag PO Box Address Undeliverable Flagad_cityhnm ad_no_uses ad_no_usep


EN8


EO8

Valuetable: TSAD12

EP8

Valuetable: TSAD12

EN9

12

EO9

4

EP9

4

EO10

DEFINITION You can put the reason for non-delivery to the Street address in this field.

EP10

DEFINITION You can put the reason for non-delivery to the PO Box address in this field.

location_model

location_id location loctype location_int

Location GUID (Length 32) External Location ID Location Type Locationbapi10002locid_32 /sapapo/ext_locno /sapapo/c_loctype /sapapo/locno


EQ4

MEANING Transfer parameter for model assignments. If a model assignment is not made for a location when it is created, the location is automatically added to the active model. However, if you do not want this automatic assignment to be made, you have to set the "NoAutoAssignmentFlag" indicator in the "SaveOptions" parameter. If model assignments are made for the location, the location is assigned only to the models specified. There is no automatic model assignment when changes are made to the location. In this case, only the model assignments specified are executed. If the "RemoveFlag" indicator is set, the location specified is removed from the model. When this happens, there is a check whether the location is still being used by location products and lanes in the model entered. If the location is still being used, it is prevented from being removed from the model and an error message is returned. RANGE DEFAULT

ES6


EQ9

32

ER9

20

ES9

4

ET9

20

EQ10


ER10


ES10


ET10


ER11


ET11


location_smtp

model remove_flag location_id

Model Name in Supply Chain Network Select an Option (Yes = 'X', No = ' ') Location GUID (Length 32)/sapapo/c_modelid bapiyesno bapi10002locid_32


EW4

MEANING Transfer parameter for the communication method 'SMTP'. Data is always replaced for communication methods. This means that any communication methods that have already been maintained for a location are replaced by the data that is transferred. However, if communication methods are not transferred for a location, the existing data is retained. The "Consnumber" field is not currently used. A number is assigned for this internally. HINTS Existing communication methods. DEFAULT

EV6

No X Yes

EU8

Valuetable: /SAPAPO/MODEL

EU9

22

EV9

1

EW9

32

EU10

DEFINITION The supply chain model is the basis for all APO planning functions. It covers all areas of the network chain from the supplier's supplier to the customer's customer. The model can be determined by importing the relevant data objects from source systems into APO, or it can be created and maintained solely in APO. The Supply Chain Engineer (SCE) is APO's modeling tool. The supply chain model includes the following entities: locations transportation lanes products resources production process models DEPENDENCIES Master data from external sources flows into the active APO model (model 000). There can be other models in APO, but none of the others receives data from external systems. A model can have several different versions which can be used for simulation purposes, but only model 000 and version 000 are active. See also planning version.

EW10


location loctype location_int

External Location ID Location Type Location/sapapo/ext_locno /sapapo/c_loctype /sapapo/locno


EY6


EX9

20

EY9

4

EZ9

20

EX10


EY10


EZ10


EX11


EZ11


std_no e_mail email_srch

Standard Sender Address in this Communication Type E-Mail Address E-Mail Address Search Fieldad_flgdfnr ad_smtpadr ad_smtpad2


FA6

X Yes No

FA9

1

FB9

241

FC9

20

FA10

DEFINITION USE If a user sends a message externally from the SAP System, their standard address is set as the sender address in the communication type used. This indicator is then important if several addresses are maintained for one communication type. DEPENDENCIES EXAMPLE In a mail system group, the users receive all messages in their Microsoft Exchange P.O. boxes. In the standard communication type of SAP users (Internet mail), the address of their Exchange P.O. boxes is set as the home address and their Internet address in the SAP System is set as the standard address. A user sends an Internet message from the SAP System. The standard address for the communication type Internet mail [email protected] is used as the sender address. If a reply is sent to this address, the user receives it in his or her Exchange P.O. box that his or her home address refers to.

FB10

DEFINITION Internet mail address, also called e-mail address. Example: [email protected] The Internet mail address is used to send mail via the Internet world-wide; the protocol used is SMTP (Simple Mail Transfer Protocol). The Internet mail address format is specified in various RFCs (Internet Request for Comment), including RFCs 821 and 822. This is not an IP address (192.56.30.6).

FC10

DEFINITION This field is generated by the system from the complete Internet mail address and is stored in table ADR6. It contains the first 20 characters of the Internet mail address in normalized form, that is, without comment characters and converted into uppercase. The field cannot be maintained by the user or from an interface. The table ADR6 contains an index for this field. Using an Internet mail address, the corresponding key of table ADR6 and the owner of the address are determined (for example, business partner or user).

std_recip r_3_user

Flag: Recipient is standard recipient for this number Flag: connected to R/3ad_dftrcnr ad_r3_user

char/ 1/ char/ 1/

FD6

X Yes No

FE6

X Yes No

FD9

1

FE9

1

encode tnef

Desired Data Coding (E-Mail) Flag: Receiver can receive TNEF coding via SMTPad_encode ad_tnef6

char/ 1/ char/ 1/

FF6

0 NONE 1 MIME 2 UUENCODE

FG6

X Yes No

FF9

1

FG9

1

home_flag consnumber

Recipient address in this communication type (mail sys.grp) Sequence numberad_flghome ad_consnum

char/ 1/ numc/ 3/

FH6

X Yes No

FH9

1

FI9

3

FH10

DEFINITION USE All messages in a mail system group are sent to the home address of the recipient in his or her standard communication type. DEPENDENCIES The standard communication type for internal users is maintained in the personal office settings (SO12). The mail system group is activated in the shared office settings (SO16). EXAMPLE The users in a mail system group receive all messages in their Microsoft Exchange P.O. boxes. SAP users have Internet mail as their standard communication type and the address of their Exchange P.O. boxes as their home addresses. An SAP application sends a message to the internal user Braun. The message is automatically forwarded to his home address [email protected], that is, his Exchange P.O. box.

location_fax

flg_nouse location_id location

Flag: This Communication Number is Not Used Location GUID (Length 32) External Location IDad_flnouse bapi10002locid_32 /sapapo/ext_locno


FK4

MEANING Transfer parameter for the communication method 'fax'. Data is always replaced for communication methods. This means that any communication methods that have already been maintained for a location are replaced by the data that is transferred. However, if communication methods are not transferred for a location, the existing data is retained. The "Consnumber" field is not currently used. A number is assigned for this internally. HINTS Existing communication methods. DEFAULT

FJ6

X Yes No

FJ9

1

FK9

32

FL9

20

FJ10

DEFINITION Set this flag if you know that this communication number is not to be used. EXAMPLE A customer has told a Call Center that he or she does not want to be called under a particular telephone number. Set this flag for this telephone number. The Call Center example also shows why you should set the flag rather than delete the communication number. The system recognizes the caller from the inbound telephone number. The number is still required in the system to support processes for inbound communication even though it may no longer be called. Similar examples apply to other communication methods, such as fax or e-mail.

FK10


FL10


FL11


loctype location_int country countryiso

Location Type Location Country for telephone/fax number Country ISO code/sapapo/c_loctype /sapapo/locno ad_comctry intca


FM6


FO8

Valuetable: T005

FM9

4

FN9

20

FO9

3

FP9

2

FM10


FN10


FO10

DEFINITION The country for the telephone number or fax number is maintained here. This specification is used to determine the correct country code. A normalized form of the telephone number or fax number is then derived and stored in a field for a program-driven search. In most cases, the telephone number or fax number refers directly to an address. If this is the case, when a new number is created, the country of the address is proposed. If this is not the case (for example, with address-independent communication data for a business partner), the country from the user parameter LND is proposed (if it is maintained). If the user parameter LND is not maintained, the country of the company address assigned in the user master data is proposed. HINTS If the country of the address changes, the country of the corresponding telephone number and fax address is not changed automatically. Example: A business partner moves abroad. If the telephone number is for a permanent connection, the telephone number also changes when the business partner moves and has to be maintained again in the system. If the telephone number is for a mobile telephone and the number is retained, the original country for this telephone number also has to be retained and must not be changed automatically to the new country of the address.

FP10


FN11


std_no fax

Standard Sender Address in this Communication Type Fax number: dialling code+numberad_flgdfnr ad_fxnmbr

char/ 1/ char/ 30/

FQ6

X Yes No

FQ9

1

FR9

30

FQ10


extension fax_no sender_no

Fax no.: Extension Complete number: dialling code+number+extension Fax number for finding senderad_fxxtns ad_fxnrlng ad_faxnrcl


FS9

10

FT9

30

FU9

30

FT10

DEFINITION The content of this field is automatically calculated by the system based on fax number and country code components. This field is therefore not to be filled when Business Address Services function modules are called.

FU10

DEFINITION The content of this field is automatically calculated by the system based on fax number and country code components. This field is therefore not to be filled when Business Address Services function modules are called. Specific applications can ensure that a deviating value can be transferred to this field, when certain BAS function modules are called with the parameter ACCEPT_TELNR_CALL.

fax_group std_recip r_3_user

Fax group (G3, G4, ...) Flag: Recipient is standard recipient for this number Flag: connected to R/3ad_fxgrp ad_dftrcnr ad_r3_user


FV6

3 G3 4 G4

FW6

X Yes No

FX6

X Yes No

FV9

1

FW9

1

FX9

1

home_flag consnumber

Recipient address in this communication type (mail sys.grp) Sequence numberad_flghome ad_consnum

char/ 1/ numc/ 3/

FY6

X Yes No

FY9

1

FZ9

3

FY10


location_tel

flg_nouse location_id location

Flag: This Communication Number is Not Used Location GUID (Length 32) External Location IDad_flnouse bapi10002locid_32 /sapapo/ext_locno


GB4

MEANING Transfer parameter for the communication method 'Telephone'. Data is always replaced for communication methods. This means that any communication methods that have already been maintained for a location are replaced by the data that is transferred. However, if communication methods are not transferred for a location, the existing data is retained. The "Consnumber" field is not currently used. A number is assigned for this internally. HINTS Existing communication methods. DEFAULT

GA6

X Yes No

GA9

1

GB9

32

GC9

20

GA10


GB10


GC10


GC11


loctype location_int country countryiso

Location Type Location Country for telephone/fax number Country ISO code/sapapo/c_loctype /sapapo/locno ad_comctry intca


GD6


GF8

Valuetable: T005

GD9

4

GE9

20

GF9

3

GG9

2

GD10


GE10


GF10

DEFINITION The country for the telephone number or fax number is maintained here. This specification is used to determine the correct country code. A normalized form of the telephone number or fax number is then derived and stored in a field for a program-driven search. In most cases, the telephone number or fax number refers directly to an address. If this is the case, when a new number is created, the country of the address is proposed. If this is not the case (for example, with address-independent communication data for a business partner), the country from the user parameter LND is proposed (if it is maintained). If the user parameter LND is not maintained, the country of the company address assigned in the user master data is proposed. HINTS If the country of the address changes, the country of the corresponding telephone number and fax address is not changed automatically. Example: A business partner moves abroad. If the telephone number is for a permanent connection, the telephone number also changes when the business partner moves and has to be maintained again in the system. If the telephone number is for a mobile telephone and the number is retained, the original country for this telephone number also has to be retained and must not be changed automatically to the new country of the address.

GG10


GE11


std_no telephone

Standard Sender Address in this Communication Type Telephone no.: dialling code+numberad_flgdfnr ad_tlnmbr

char/ 1/ char/ 30/

GH6

X Yes No

GH9

1

GI9

30

GH10


extension tel_no

Telephone no.: Extension Complete number: dialling code+number+extensionad_tlxtns ad_telnrlg

char/ 10/ char/ 30/

GJ9

10

GK9

30

GK10

DEFINITION The content of this field is automatically calculated by the system based on the telephone number and country code components. This field is therefore not to be filled when Business Address Services function modules are called.

caller_no std_recip

Telephone number for determining caller Flag: Recipient is standard recipient for this numberad_telnrcl ad_dftrcnr

char/ 30/ char/ 1/

GM6

X Yes No

GL9

30

GM9

1

GL10

DEFINITION The content of this field is automatically calculated by the system based on the telephone number and country code components. This field is therefore not to be filled when Business Address Services function modules are called. Specific applications (for example, SAPphone) can ensure that a deviating value can be transferred in this field, when certain BAS function modules are called with the parameter ACCEPT_TELNR_CALL.

r_3_user home_flag

Flag: connected to R/3 Recipient address in this communication type (mail sys.grp)ad_r3_user ad_flghome

char/ 1/ char/ 1/

GN6

X Yes No

GO6

X Yes No

GN9

1

GO9

1

GO10


location_uri

consnumber flg_nouse location_id

Sequence number Flag: This Communication Number is Not Used Location GUID (Length 32)ad_consnum ad_flnouse bapi10002locid_32

numc/ 3/ char/ 1/ char/ 32/

GR4

MEANING Transfer parameter for the communication method 'URI'. Data is always replaced for communication methods. This means that any communication methods that have already been maintained for a location are replaced by the data that is transferred. However, if communication methods are not transferred for a location, the existing data is retained. The "Consnumber" field is not currently used. A number is assigned for this internally. HINTS Existing communication methods. DEFAULT

GQ6

X Yes No

GP9

3

GQ9

1

GR9

32

GQ10


GR10


location loctype location_int

External Location ID Location Type Location/sapapo/ext_locno /sapapo/c_loctype /sapapo/locno


GT6


GS9

20

GT9

4

GU9

20

GS10


GT10


GU10


GS11


GU11


std_no uri_type

Standard Sender Address in this Communication Type URI type flagad_flgdfnr ad_uritype

char/ 1/ char/ 3/

GV6

X Yes No

GW6

HPG Homepage (WWW) FTP FTP address STK Callup share prices ACC Bank statement request INT Intranet page LOG Company logo PFB Published Free/Busy information (calendar) ROU Link to Route Planner

GV9

1

GW9

3

GV10


uri std_recip

URI, e.g. Homepage or ftp Address Flag: Recipient is standard recipient for this numberad_uriscr ad_dftrcnr

char/ 132/ char/ 1/

GY6

X Yes No

GX9

132

GY9

1

GX10

Enter a URI. URI means Universal Resource Identifier (cf. Internet specification rfc 1630). The system contains various types of URIs, but they all have the same format. The most common URIs are homepage addresses (type HPG), others include ftp addresses. URIs of up to 2048 characters can be entered in the system via BAPI interfaces, in dialog the maximum length is 132 characters.

home_flag

Recipient address in this communication type (mail sys.grp)ad_flghome

char/ 1/

GZ6

X Yes No

GZ9

1

GZ10


uri_part1 uri_part2

Universal Resource Identifier (URI): Parts 1-8 Universal Resource Identifier (URI): Parts 1-8ad_uri_1 ad_uri_1

char/ 250/ char/ 250/

HA9

250

HB9

250

uri_part3 uri_part4


char/ 250/ char/ 250/

HC9

250

HD9

250

uri_part5 uri_part6


char/ 250/ char/ 250/

HE9

250

HF9

250

uri_part7 uri_part8


char/ 250/ char/ 250/

HG9

250

HH9

250

uri_part9 consnumber

Universal Resource Identifier (URI) - Part 9 Sequence numberad_uri_9 ad_consnum

char/ 48/ numc/ 3/

HI9

48

HJ9

3

flg_nouse

Flag: This Communication Number is Not Usedad_flnouse

char/ 1/

HK6

X Yes No

HK9

1

HK10


logical_system

logical_system


-> documentation

char/ 10/

A1

bapi_prdsrvaps_savemulti2

B1

bapi_prdsrvaps_getlist2

A2

FUNCTIONALITY You can use this method to create and change products. If the product with the key specified already exists, it is changed. However, if it does not exist it is newly created. Note that the product can only be created if the external key ("Product") was also provided. To change products that already exist, you can use both the internal key ("ProductId" or "ProductInt") and external key. In general, products can only be created or changed if they exist in the business system group to which the logical system specified belongs ("LogicalSystem"). HINTS Note that it is currently possible to work with a planning version during a method call only. If several different planning versions are specified in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority", processing is terminated and an error message is issued. If the data entered in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" is planning-version-independent, the "PlanningVersion" field must be empty or contain the value "000". It is not possible to set planning-version-dependent data for the active planning version only ("000"). The data for the active planning version is always also valid for the other planning versions if specific, planning-version-dependent data has not been maintained for them. When this method is executed, no database locks are set and evaluated, since the interface has highest priority. You can find information about classifying products here. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information.

B2

FUNCTIONALITY You can use this method to read products for certain selection criteria. HINTS There are the following options for selecting the products. Combinations of the alternatives are not possible or are ignored. Selection by entering the product GUID "ProductGuids" Selection using RANGES tables: The following combinations can be used for this: "ProductSelection" + "ModelSelection" (optional) + "BsgSelection" (optional) + "LocationSelection" (optional) + "LoctypeSelection" (optional) "ProductIntSelection" + "ModelSelection" (optional) + "BsgSelection" (optional) + "LocationIntSelection" (optional) + "LoctypeSelection" (optional) Selection using explicit keys: "ProductKey" "ProductIntKey" In addition to the three selection variants, you can use the "PlanningVersionSelection" parameter to restrict the planning version for which data is to be returned in the "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" parameters. If the parameter is empty, only planning-version-independent default values are returned. If the selection is made using internal keys ("ProductIntSelection", "LocationIntSelection", "ProductIntKey") or Guids ("ProductGuids"), the external keys are not filled in the return parameters. Only the internal keys are returned. If you want to determine the associated external key, you have read in the "ProductMapping" or "LocationMapping" parameter using the internal key and business system group. Note that this method can read data for products from different business system groups. There is no restriction to the business system group to which the logical system specified belongs ("LogicalSystem"). The classification of products is seen as a separate object. For more information, see here. In general, you are only recommended to read the parameters that are actually needed. For more information, see the documentation for the "ExcludeExportFlags" parameter. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information Using internal selection

B4


B8


B9

10

B10


product_head

product_id product product_int gtin_flag

Product GUID (Length 32) External Product Indicator Product ID EAN/UPC Indicatorbapi10001matid_32 /sapapo/ext_matnr /sapapo/matnr /sapapo/gtin_ind


C4

MEANING Transfer parameter for general product data. RANGE DEFAULT HINTS The Base Unit of Measure is only used when creating products. It is not possible to subsequently change the base unit of measure for products. If the "GtinFlag" indicator is set, the product ID in APO is interpreted as a GTIN ("Global Trade Item Number").

F6

X Yes No

D8

Valuetable: /SAPAPO/MATMAP

E8

Conversion Exit: PRODU

C9

32

D9

40

E9

40

F9

1

C10


D10

DEFINITION Product name used in the BSG in which the product was created.

E10

DEFINITION Alphanumerical key that uniquely identifies a product.

F10

DEFINITION Indicates that the product number corresponds to an EAN or a UPC. USE Set the EAN/UPC indicator if the product number corresponds to an EAN or a UPC. The EAN/UPC indicator is used in Responsive Replenishment. DEPENDENCIES EXAMPLE

D11

BAPI10001PRODUCTHELP/PRODUCT_EXT

E11

BAPI10001PRODUCTHELP/PRODUCT_INT

base_uom base_uom_iso material_group transportation_group

Base Unit of Measure ISO code for unit of measurement Material Group Transportation Group/sapapo/meins isocd_unit /sapapo/matkl /sapapo/tragr


G8


H8

Valuetable: T006I

J8

Valuetable: /SAPAPO/TTGR

G9

3

H9

3

I9

9

J9

4

G10

DEFINITION Unit of measure used for keeping inventory of a product. The system converts all quantities that you record in other units into the base unit of measure. (Alternative units of measure) USE WHAT_TO_DO EXAMPLES DEPENDENCIES It is especially important to establish the base unit of measure as it is the basis for all data updates and plays a vital role in the conversion into alternative units of measure. An exact conversion of a quantity into an alternative unit of measure can only take place if its value can be represented with the decimal places available. In order to ensure this, note the following points: The base unit of measure is the one that most closely satisfies the exact requirements. The conversion from alternative units of measure to the base ones should result in simple decimal fractions (in other words not 1/3 = 0,333...). Service industries have their own units of measure. For example: SU Service unit (Unit of measure on a level higher than the position. The exact entries for individual production units are always included on the detailed level of the service line). FR Flat rate (Unit of measure on the service line level for one-time services for which it is not possible or necessary to enter exact amounts).

H10


I10

DEFINITION Product information transferred from OLTP system or R/3 System.

J10

DEFINITION Groups products with the same transportation requirements. USE EXAMPLE You sell foodstuffs. If you want to transport food that spoils easily and that must be kept cool during transportation, you create a transportation group for products that have to be transported in a refrigerated truck.

product_hierarchy stacking_factor planning_usage

Product Hierarchy Stacking Factor Usage in Demand Planning and Supply Network Planning/sapapo/prdha /sapapo/stfac /sapapo/ts_sdp_use

char/ 18/ numc/ 2/ char/ 1/

M6

Relevant for DP and SNP 1 Not Relevant for SNP or DP 2 Relevant for SNP; Not Relevant for DP

K9

18

L9

2

M9

1

L10

DEFINITION The stacking factor indicates how often a pallet of this product can be stacked, and the manner in which the pallet should be stacked. DEPENDENCIES You maintain the minimum/maximum number of pallet stacks per transport unit via Supply Chain Planning -> Supply Network Planning -> Environment -> Current settings -> Define profile for the Transport Load Builder (TLB) . EXAMPLE If you enter a 5, you can stack five pallets on top of each other. Note: If the pallets cannot be stacked, enter 1. If no entries are made in this field, the system assumes that the pallets cannot be stacked.

M10

DEFINITION USE This field enables you to exclude products from Demand Planning (DP) and/or Supply Network Planning (SNP). Since end products and main components are primarily relevant to SNP, for example, you can specify that subcomponents are not to be planned in SNP. In this way, you can restrict the number of planned products. If you leave this field empty (default value), the product will be planned in DP and SNP. DEPENDENCIES EXAMPLE

shelf_life_flag shelf_life maturation_time

Planning with Reference to Product Shelf Life Shelf Life Maturation Time/sapapo/shelf_life_flag /sapapo/shelf_life_dur /sapapo/maturity_dur

char/ 1/ dec/ 11/ 0 dec/ 11/ 0

N6

X Yes No

O8

Conversion Exit: TSTRG

P8


N9

1

O9

10

P9

10

N10

DEFINITION If you set the 'Planning with Shelf Life' indicator for the product, the system takes into account both the maturity and shelf life of product receipts, as well as shelf life requirements, when planning this product. WHAT_TO_DO The value is transferred by means of the CIF interface. You can change the value.

O10

DEFINITION Period within the shelf life of the material, that is, from the time of receipt to the time of expiry. USE The maturity time defined in the product master is transferred to all product receipts (such as production and stock transfer orders) that are generated in APO. The system considers the maturity time of a product receipt during pegging. A product requirement can only make use of a product receipt if the requirements time occurs outside the maturity time of the receipt. WHAT_TO_DO The system transfers the value by means of the CIF interface. You can change the value. To do so, specify the number of days for the shelf lifen. DEPENDENCIES The maturity time is part of the shelf life period. The maturity time of a product is only considered during planning if the indicator "Planning with shelf life" has been set in the product master.

P10

DEFINITION The period required by a product after production before it can be used for further production or by a customer. USE The maturation time defined in the product master is transferred to all product receipts (such as production and stock transfer orders) that are generated in APO. The system considers the maturation time of a product receipt during pegging. A product requirement can only make use of a product receipt if the requirement time occurs outside the maturation time of the receipt. WHAT_TO_DO The value is not transferred by means of the CIF interface. Enter the number of days for the maturation time. DEPENDENCIES The maturation time is part of the shelf life period. The maturation time of a product is only considered during planning if the indicator "Planning with shelf life" has been set in the product master.

req_min_shelf_life req_max_shelf_life low_level_code

Required Minimum Shelf Life Required Maximum Shelf Life Low-Level Code/sapapo/shelf_life_req_min /sapapo/shelf_life_req_max /sapapo/disst

dec/ 11/ 0 dec/ 11/ 0 char/ 3/

Q8


R8


Q9

10

R9

10

S9

3

Q10

see also data element /SAPAPO/SHELF_LIFE_REQ_MAX DEFINITION Standard value for required minimum shelf life PURPOSE If the shelf life is taken into consideration when planning a product, a product requirement can request that this should be covered by a receipt which still has a shelf life of a certain period of time. This request can be defined explicitly for the requirement (for example, in a sales order transferred from R/3). Otherwise the value entered here will be adopted as the required minimum shelf life. EXAMPLE A standard value of 4 days was defined for the required minimum shelf life in the product master data. A production order creates a receipt on 01.03.. The product shelf life is until 20.03.. A planning requirement on 08.03. can now make use of this receipt (08.03. + 5 days, that is, the receipt shelf life must be until at least 13.03., that is, before 20.03.). A planning requirement on 16.03. can not make use of this receipt (16.03. + 5 days, that is, the receipt shelf life must be until at least 21.03., that is, after 20.03.). DEPENDENCIES This value is only taken into consideration if the indicator for planning with shelf life is set in the product master data ('Planning with shelf life') the requirement element does not have an explicit request for the shelf life

R10

see also data element /SAPAPO/SHELF_LIFE_REQ_MIN DEFINITION Standard value for required maximum shelf life PURPOSE If the shelf life is taken into consideration when planning a product, a product requirement can request that this should be covered by a receipt which does not exceed a certain shelf life. This request can be defined explicitly for the requirement (for example, in a sales order transferred to R/3). Otherwise the value entered here will be adopted as the required maximum shelf life. EXAMPLE In the product master data, the standard value for the required maximum shelf life was defined as 10 days. A production order creates a receipt on 01.03.. The product shelf life is until 20.03.. A planning requirement on 08.03 cannot make use of this receipt (08.03. + 10 days, that is, the receipt shelf life must be up to at most 18.03., that is, before 20.03.). A planning requirement on 11.03 can make use of this receipt (11.03. + 10 days, that is, the receipt shelf life must be up to at most 21.03., that is, after 20.03.). DEPENDENCIES The value is only taken into consideration if the indicator for planning with shelf life is set in the product master data ('Planning with shelf life') the requirement element does not have an explicit request for the shelf life

prd_alloc_proc

Product Allocations: Product Allocation Procedure/sapapo/kosch

char/ 18/

T8

Valuetable: /SAPAPO/T190S

T9

18

T10

DEFINITION The product allocation procedure determines how a product in limited supply is allocated to (sales) orders. The product allocation procedure can also be location-dependent (see location-dependent product allocation procedure) USE You enter the product allocation procedure in the product master record in APO or in a sequence of product allocation procedures. DEPENDENCIES In addition, different Customizing settings determine how product allocation is carried out: You can define several product allocation steps in a product allocation procedure. You assign a product allocation group to the product allocation step. The product allocation group determines the criteria that the system uses to choose a product allocation in the availability check. The consumption period determines the periods for the product allocation time series surrounding the checking date. The free product allocation quantities of these periods are then used in the confirmation invoice. The consumption periods are defined per product allocation group. You can assign several product allocation objects in the control for a product allocation step. Each object is valid for a period. The product allocation objects represent the reason for product allocation. The product allocation object is the first characteristic in the product allocation group. If you change the product allocation object, a different product allocation time series is used for the corresponding period in the check.

prd_alloc_proc_seq configurable_product_flag

Prod. Allocations: Sequence of Product Allocation Procedures Indicator: Configurable material/sapapo/kosch_grp /sapapo/kzkfg

char/ 18/ char/ 1/

V6

X Yes No

U8

Valuetable: /SAPAPO/T190L

U9

18

V9

1

U10

DEFINITION Via a sequence of product allocation procedures, several product allocation procedures are combined into a specific sequence. The sequence of product allocation procedures can also be location-dependent (see location-dependent product allocation procedure). USE The sequence of product allocation procedures determines several alternative product allocation procedures and their sequence for a product. The list of product allocation procedures is used for product allocation in the availability check. If the quantity cannot be fully confirmed in a product allocation procedure when checking, the system carries out product allocation for the remaining quantity in the next product allocation procedure in the sequence. The first product allocation procedure used is the product allocation procedure from the product master record. Every other procedure used comes from the sequence of product allocation procedures. If the product allocation procedure from the product master record appears in the list again, the system ignores it. NOTE You enter the sequence of product allocation procedures and the product allocation procedure in the product master record in APO. The sequence of product allocation procedures is only used to supplement the product allocation procedure. If a product allocation procedure has not been entered for the product, the system ignores the sequence of product allocation procedures and terminates product allocation. You can use a sequence of product allocation procedures, similar to the product allocation procedure, for several products. The range of products, for which a sequence of product allocation procedures is used, does not have to be covered with a range of products from the product allocation procedures.

reference_product reference_product_bsg attribute_1

Cross-location configurable product Business System Group Character field of length 40/sapapo/satnr /sapapo/logqs char40


W8


X8


W9

40

X9

8

Y9

40

W10

DEFINITION Number that uniquely identifies the configurable product.

X10


attribute_2 attribute_3 attribute_4 attribute_5

30 Characters Char 20 Character Field Length = 10 Character Field Length = 10char30 char20 char10 char10


Z9

30

AA9

20

AB9

10

AC9

10

vmi_prd_alloc_proc vmi_prd_alloc_proc_seq

Allocation: VMI Allocation Procedure Allocation: VMI Allocation Procedure Sequence/sapapo/vmikosch /sapapo/vmikosch_grp

char/ 18/ char/ 18/

AD8


AE8


AD9

18

AE9

18

AD10

DEFINITION The allocation procedure specifies how a product of which only a limited quantity is available is to be allocated to (sales) orders. The allocation procedure can also be location-dependent (selection: see location-dependent allocation procedure). USE You enter the allocation procedure on the APO data screen of the APO product master record or in an allocation procedure sequence. DEPENDENCIES Furthermore, various Customizing settings determine how the allocation is to be made: You can define several allocation steps in an allocation procedure. You assign an allocation group to an allocation step. The allocation group defines the criteria by which an allocation is selected in the availability check. The consumption period determines the periods of the allocation time series around the check date, whose free allocation quantity may be used for the confirmation calculation. The consumption period is defined per allocation group. In the allocation control for an allocation step, you can assign several allocation objects. Each of these objects is valid for a period. The allocation objects represent the reason for the allocation. The allocation object is the first characteristic in the allocation group. Through a change in the allocation object, a different allocation time series is used for the relevant period in the check.

AE10

DEFINITION An allocation procedure sequence groups together several allocation procedures in a certain order. The allocation procedure sequence can also be location-dependent (selection: see location-dependent allocation procedure). USE The allocation procedure sequence determines several alternative allocation procedures and their sequence for a product. The list of allocation procedures is used for during allocation in the availability check. If the quantity cannot be completely confirmed in an allocation procedure at the time of the check, the allocation is carried out for the residual quantity in the next allocation procedure of the sequence. The first allocation procedure to be used is the allocation procedure from the product master. Each further procedure comes from the allocation procedure sequence. If the allocation procedure from the product reoccurs in the list it is ignored. NOTE The allocation procedure sequence is entered on the APO data screen in the APO product master alongside the allocation procedure. The allocation procedure sequence serves as a supplement to the allocation procedure only. If no procedure has been entered for the product, the allocation procedure sequence is ignored. The allocation is then not carried out. Like the allocation procedure, an allocation procedure sequence can be used for several products. The range of products for which an allocation procedure sequence is used need not correspond to that of an allocation procedure.

max_weight max_weight_uom max_weight_uom_iso

Maximum Weight Weight Unit ISO code for unit of measurement/scwm/de_maxw /scwm/de_wgt_uom isocd_unit

quan/ 15/ 3 unit/ 3/ char/ 3/

AF8

Reference Table: BAPI10001PRD2 Reference Field: MAX_WEIGHT_UOM

AG8


AH8

Valuetable: T006I

AF9

19

AG9

3

AH9

3

AG10

DEFINITION Unit referring to the gross weight or net weight of the material. USE WHAT_TO_DO If you specify a weight, you must enter the corresponding unit of weight here. EXAMPLES DEPENDENCIES

AH10


excess_weight_tolerance max_volume max_volume_uom

Excess Weight Tolerance for Handling unit Maximum Allowed Volume Volume Unit/scwm/de_maxw_tol /scwm/de_maxv /scwm/de_vol_uom

dec/ 3/ 1 quan/ 15/ 3 unit/ 3/

AJ8

Reference Table: BAPI10001PRD2 Reference Field: MAX_VOLUME_UOM

AK8


AI9

4

AJ9

19

AK9

3

AI10

DEFINITION Specifies the tolerance limit for the maximum allowed loading weight of a packaging material for this packing. HINTS The tolerance is taken into account during both manual and automatic packing.

AK10

DEFINITION Unit referring to the volume of the material. WHAT_TO_DO If you specify a volume, you have to enter the corresponding volume unit here.

max_volume_uom_iso excess_volume_tolerance

ISO code for unit of measurement Excess Volume Tolerance of the Handling Unitisocd_unit /scwm/de_maxv_tol

char/ 3/ dec/ 3/ 1

AL8

Valuetable: T006I

AL9

3

AM9

4

AL10


AM10

DEFINITION Specifies the tolerance limit for the maximum packing volume for a packaging material. HINTS The tolerance is taken into account during both manual and automatic packing.

max_capacity excess_capacity_tolerance

Maximum Permitted Capacity Key Figure Excess Capacity Tolerance of Handling Unit/scwm/de_maxc /scwm/de_maxc_tol

dec/ 15/ 3 dec/ 3/ 1

AN9

19

AO9

4

AO10

DEFINITION Defines the tolerance limit for the maximum packaging capacity of a packaging material. HINTS The tolerance is taken into account during both manual and automatic packing.

packaging_material_type closed_box_flag fill_level

Packaging Material Type Packaging Material is Closed Packaging Filling Level (By Volume)/scwm/de_pmtyp /scwm/de_closed_pm /scwm/de_max_fill_up

char/ 4/ char/ 1/ dec/ 3/ 0

AQ6

X Yes No

AP8

Valuetable: /SCWM/TPMTYP

AP9

4

AQ9

1

AR9

3

AP10

WHAT_TO_DO Enter a code and a description for a group of similar materials (such as crates, trucks, or pallets). USE The packaging material type that you enter here is connected with a packaging material group in Customizing, which you assign to a product/ material in the material master. When you construct a handling unit, you call up a list of all packaging materials that allowed for the item to pack. The system creates this list by determining the relevant packaging material types for the packaging material group for the item to pack EXAMPLE Packaging material group Packaging material types 0001 Drinks 0010 Barrel 0001 Drinks 0020 Bottle 0002 Small parts 0030 Crate 0002 Small parts 0040 Plastic bag 0003 Pallet 0050 Container 0003 Pallet 0060 Truck During packing, if you call up a list of all allowed packaging materials for a material to be packed (for which you have defined the packaging material group 0001 (Drinks) in the material master), the system lists all packaging materials of type 0010 (Barrel) and 0020 (Bottle). For packaging material group 0002 (Small parts), the system suggests packaging material of type 0030 (Crate) and 0040 (Plastic bag), and for packaging material group 0003, the system suggested packaging materials NOTE You can define the packaging material group and the packaging material types as you wish.

AQ10

DEFINITION For closed packaging materials, during packing the total volume is not increased by the loading volume of the contents. EXAMPLE For a crate, the total volume is the same whether it is empty or full. This means that a crate is a closed packaging material. For a pallet, the total volume is a result of the tare volume of the pallet and the loading volume. The pallet is an open packaging material.

AR10

DEFINITION Maximum level (by volume) USE Enter the maximum level (in percent) up to which the packaging material should be filled. DEPENDENCIES This field is only for information purposes. EXAMPLE

handling_unit_type own_weight_variable_flag packing_group packing_reference_product

Handling Unit Type Tare Weight Variable Packing Group External Product Indicator/scwm/de_hutyp /scwm/de_tare_var /scwm/de_packgr /sapapo/ext_matnr


AT6

X Yes No

AS8

Valuetable: /SCWM/THUTYP

AU8

Valuetable: /SCWM/TPACKGR

AV8


AS9

4

AT9

1

AU9

4

AV9

40

AT10

DEFINITION Flags all packaging materials for this packaging material type as packaging materials with a variable tare weight. If a change in the total weight occurs, then the tare weight is adjusted and not the loading weight. USE Use this indicator if you cannot determine exactly the tare weight for packaging materials in this packaging material type, but the weights in your materials to be packed are relatively accurate. DEPENDENCIES EXAMPLE Individually constructed crates and pallets that do not comply with any standards.

AV10


product_text

packing_reference_product_bsg display_indicator product_id

Business System Group Display Product GUID (Length 32)/sapapo/logqs /sapapo/disp bapi10001matid_32


AY4

MEANING Transfer parameter for language-dependent short texts. RANGE DEFAULT

AW8


AW9

8

AX9

1

AY9

32

AW10


AX10

DEFINITION The display indicator shows whether a product is used for a sales promotion. USE If the display indicator is set, the product is used for a sales promotion. DEPENDENCIES EXAMPLE

AY10


product product_int langu langu_iso

External Product Indicator Product ID Language Key Language according to ISO 639/sapapo/ext_matnr /sapapo/matnr langu laiso

char/ 40/ char/ 40/ lang/ 1/ char/ 2/

AZ8


BA8


BB8


AZ9

40

BA9

40

BB9

2

BC9

2

AZ10


BA10


BB10

DEFINITION The Language key field contains an alphanumeric code that identifies the language an entry is written in. USE In DISPLAY mode, this field identifies the language a record is written in. In CREATE mode, use this field to identify the language you will use to enter a description. To do so either: Type in the appropriate code, or Request a list of language codes and make a selection by either: . Pressing F4, or . Clicking the down arrow NOTE: It is not possible to make entries in this field, everywhere in the system. Sometimes the system automatically completes the field, and you may not change it.

AZ11


BA11


product_alt_uom

prd_descr product_id product product_int

Product Description Product GUID (Length 32) External Product Indicator Product ID/sapapo/maktx bapi10001matid_32 /sapapo/ext_matnr /sapapo/matnr


BE4

MEANING Transfer parameter for alternative units of measure . RANGE DEFAULT

BF8


BG8


BD9

40

BE9

32

BF9

40

BG9

40

BE10


BF10


BG10


BF11


BG11


alternative_uom alternative_uom_iso

Alternative Unit of Measure ISO code for unit of measurement/sapapo/lrmei /sapapo/isocd_unit

unit/ 3/ char/ 3/

BH8


BI8

Valuetable: T006I

BH9

3

BI9

3

BH10

DEFINITION Unit of measure that can be used as an alternative to the base unit of measure.

numerator

Numerator for Conversion to Base Units of Measure/sapapo/umrez

dec/ 5/ 0

BJ9

6

BJ10

DEFINITION Counter of the quotient which indicates the relationship between the AME and the Base unit of measurement. USE In order to convert a quantity with a different unit of measure to the base unit of measure, the system requires a quotient: Quantity (in the alternative unit of measure) = quotient * quantity (in base unit of measure). Specify how many units in the alternative unit of measure (in the denominator) correspond to how many base units of measure (in the counter). You can only enter whole numbers in the fields for the counter and denominator, which means 3.14 m2 correspond to one piece, you must enter a multiple in whole numbers (314 m2 = 100 pieces). The quotient is therefore 100/314 in this case, the counter 100 and the denominator 134. EXAMPLE The alternative unit of measure is kilogram (kg). The base unit of measure is piece (pc). 5kg correspond to 3 pieces. ,,,,5 kg = 3 pcs -> 1 kg = 3/5 pc The quotient in this case is therefore 3/5, the counter 3 and the denominator 5.

denominator international_article_number gross_weight

Denominator for conversion to base units of measure International Article Number Gross Weight/sapapo/umren /sapapo/ean11 /sapapo/brgew

dec/ 5/ 0 char/ 18/ quan/ 13/ 3

BM8

Reference Table: BAPI10001PRDALTUOM2 Reference Field: WEIGHT_UOM

BK9

6

BL9

18

BM9

17

BK10

DEFINITION Denominator of the quotient which indicates the relationship between the AME and the Base unit of measurement. USE In order to convert a quantity with a different unit of measure to the base unit of measure, the system requires a quotient: Quantity (in the alternative unit of measure) = quotient * quantity (in base unit of measure). Specify how many units in the alternative unit of measure (in the denominator) correspond to how many base units of measure (in the counter). You can only enter whole numbers in the fields for the counter and denominator, which means 3.14 m2 correspond to one piece, you must enter a multiple in whole numbers (314 m2 = 100 pieces). The quotient is therefore 100/314 in this case, the counter 100 and the denominator 134. EXAMPLE The alternative unit of measure is kilogram (kg). The base unit of measure is piece (pc). 5kg correspond to 3 pieces. ,,,,5 kg = 3 pcs -> 1 kg = 3/5 pc The quotient in this case is therefore 3/5, the counter 3 and the denominator 5.

BL10

DEFINITION Internationally standardized number that uniquely identifies a specific material. This number always relates to a particular unit of measure or type of packaging. The European Article Number (EAN) is normally assigned by the manufacturer of the material. In this case, the EAN also identifies the manufacturer uniquely. A company can also assign EANs using various "in-store" numbering techniques. An instore EAN is known only to the respective company. The equivalent of the EAN in America is the UPC (Universal Product Code).

net_weight weight_uom weight_uom_iso volume volume_uom

Net weight Weight unit ISO code for unit of measurement Volume Volume Unitntgew /sapapo/gewei /sapapo/isocd_unit /sapapo/volum /sapapo/voleh

quan/ 13/ 3 unit/ 3/ char/ 3/ quan/ 13/ 3 unit/ 3/

BN8

Reference Table: BAPI10001PRDALTUOM2 Reference Field: WEIGHT_UOM

BO8


BP8

Valuetable: T006I

BQ8

Reference Table: BAPI10001PRDALTUOM2 Reference Field: VOLUME_UOM

BR8


BN9

17

BO9

3

BP9

3

BQ9

17

BR9

3

BN10

DEFINITION Net weight expressed in the unit of weight specified by you in the Unit of weight field.

BO10

Provides a common unit of measure for different products. Indicates the unit of measure associated with the minimum and maximum weight. This unit may be distinct from the unit defined in the transportation resource master. Indicates the base unit used to calculate the weight of the product to be transported, per transport order item. (During the TLB run, individual transport order items are grouped together to create a feasible transport order.) The system measures weight in the unit specified in the product master, Attributes tab, Gross weight field. Indicates the capacity (in weight) still available on the transport vehicle per transport order. (During the TLB run, individual transport order items are grouped together to create a feasible transport order.) The system measures free weight capacity based on the capacity specified in the TLB profile, Weight capacity field. Indicates the base unit used to calculate the cumulative weight of the products included in this transport order. (During the TLB run, individual transport order items are grouped together to create a feasible transport order.) The system measures cumulative weight in the unit specified in the TLB profile, Weight unit field. Indicates the base unit used to calculate the weight of the transport order. Resource master Product master

BR10

Provides a common unit of measure for different products. Indicates the unit of measure associated with the minimum and maximum volume. This unit may be distinct from the unit defined in the transportation resource master. Indicates the base unit used to calculate the volume of the products included in a particular transport order per transport order item. (During the TLB run, individual transport order items are grouped together to create a feasible transport order.) The system measures volume in the unit specified in the product master, Attributes tab, Volume field. Indicates the base unit used to calculate the cumulative volume of the products included in the transport order. (During the TLB run, individual transport order items are grouped together to create a feasible transport order.) The system measures cumulative volume capacity in the unit specified in the TLB profile, Volume unit field. Resource master Product master TLB profile

volume_uom_iso length width height

ISO code for unit of measurement Length Width Height/sapapo/isocd_unit laeng breit hoehe

char/ 3/ quan/ 13/ 3 quan/ 13/ 3 quan/ 13/ 3

BS8

Valuetable: T006I

BT8

Reference Table: BAPI10001PRDALTUOM2 Reference Field: DIMENSION_UOM

BU8


BV8


BS9

3

BT9

17

BU9

17

BV9

17

BT10

DEFINITION Length of the material or its packaging, measured in the unit of dimension.

BU10

DEFINITION Breadth of the material or its packaging, measured in the unit of dimension.

BV10

DEFINITION Height of the material or its packaging, measured in the unit of dimension.

dimension_uom dimension_uom_iso capacity_consumption

Unit of Dimension for Length/Width/Height ISO code for unit of measurement Capacity Usagemeabm /sapapo/isocd_unit /scwm/de_capause

unit/ 3/ char/ 3/ dec/ 15/ 3

BW8


BX8

Valuetable: T006I

BW9

3

BX9

3

BY9

19

BW10

DEFINITION Unit in which the dimensions of length, breadth, and height of a material or its packaging are measured.

product_penalty

product_id product product_int requirement_type

Product GUID (Length 32) External Product Indicator Product ID Requirements Typebapi10001matid_32 /sapapo/ext_matnr /sapapo/matnr /sapapo/snpdemcld

char/ 32/ char/ 40/ char/ 40/ numc/ 1/

BZ4

MEANING Transfer parameter for product-dependent penalty costs. RANGE DEFAULT

CC6

1 Regard as a customer demand 5 Regard as corrected demand forecast 6 Regard as demand forecast

CA8


CB8


BZ9

32

CA9

40

CB9

40

CC9

1

BZ10


CA10


CB10


CC10

DEFINITION The demand priority is used in the demand calculation. WHAT_TO_DO Enter the demand priority defined in the ATP category groups in ATP customizing.

CA11


CB11


non_delivery_penalty

Penalty for Not Delivering (Costs per Base Unit of Measure)/sapapo/snpndpend

dec/ 13/ 3

CD9

17

CD10

Definition Here you specify penalty costs for not delivering requested product quantities. The SNP optimizer uses these penalty costs within its calculations. Use You can specify the penalties for not delivering customer requirements, the demand forecast, and the corrected demand forecast separately. You have the option here of dividing the demand forecast into two different key figures and giving each one a different weighting. For example, you can give already existing forecasts (demand forecasts) a different weighting to new forecasts (corrected demand forecast). You can also specify time-dependent penalty costs and, thus, assign a time priority to requirements. To do this select the corresponding pushbutton with the Create Time-Dependent Penalty Costs quick info and enter a penalty cost validity end date. Dependencies The system uses the base unit of measure defined in the product master to calculate this penalty. It considers customer requirements as priority 1, the corrected demand forecast as priority 2, and the demand forecast as priority 3. The SNP optimizer first calculates the penalty costs on a location-dependent basis, then on a non-location-dependent basis.

delayed_delivery_penalty max_delay

Delay Penalty (Costs per Day and Base Unit of Measure) Maximum Allowed Delay (in Days)/sapapo/snplapend /sapapo/snpmaxlad

dec/ 13/ 3 dec/ 3/ 0

CE9

17

CF9

3

CE10

Definition Gives the penalty cost rate per day that is used by the SNP Optimizer to weight the delayed delivery of a product with regard to the planned delivery date. The penalty for delayed delivery of the requirement quantities is measured per base unit of quantity. Use You can set separately the delay penalties for customer requirements, the requirement forecast and the corrected requirements forecast. You thus have the opportunity to divide the requirements forecast into two different indicators and to weight these differently. You can, for example, weight those forecasts already available (requirements forecast) differently to new forecasts (corrected requirements forecast). You can also define time-dependent penalty costs and, therefore, assign a time priority to requirment. To do this, select the corresponding pushbutton with quick info text Create Time-Dependent Penalty Costs. Dependencies To calculate this penalty the system uses the base unit of quantity defined in the product master. Customer requirements are viewed as Priority 1 by the system, the corrected requirement forecast as priority 3 and the requirement forecast as priority 3.

CF10

Indicates the maximum number of days a product can be late. After the maximum late date has passed, the system stops calculating late penalties and determines the non-delivery penalties. You can also define the maximum number of days a product can be late as time-dependent. To do this, select the corresponding pushbutton with quick info text Create Time Dependent Penalty Costs.

date_valid_to

Time stamp at end of validity period/sapapo/scc_valtotstmp

dec/ 15/ 0

CG9

19

logical_system

logical_system


-> documentation

char/ 10/

M026 - FG AP CARAPDCLNT001APDCLNT001APDCLNT001APDCLNT001

M026 - FOR FG AP CARAPDCLNT001APDCLNT001APDCLNT001APDCLNT001

M026 - RM / PM AP FGCARAPDCLNT001APDCLNT001APDCLNT001APDCLNT001APDCLNT001

M026 - FG AP MINI FRESHAPDCLNT001APDCLNT001APDCLNT001APDCLNT001

M026 - FG AP MINI FRESH (CHINA)APDCLNT001APDCLNT001APDCLNT001

M026 - RM / PM AP MINIFRESHAPDCLNT001APDCLNT001APDCLNT001

A1

bapi_prdsrvaps_savemulti2

B1

bapi_prdsrvaps_getlist2

A2

FUNCTIONALITY You can use this method to create and change products. If the product with the key specified already exists, it is changed. However, if it does not exist it is newly created. Note that the product can only be created if the external key ("Product") was also provided. To change products that already exist, you can use both the internal key ("ProductId" or "ProductInt") and external key. In general, products can only be created or changed if they exist in the business system group to which the logical system specified belongs ("LogicalSystem"). HINTS Note that it is currently possible to work with a planning version during a method call only. If several different planning versions are specified in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority", processing is terminated and an error message is issued. If the data entered in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" is planning-version-independent, the "PlanningVersion" field must be empty or contain the value "000". It is not possible to set planning-version-dependent data for the active planning version only ("000"). The data for the active planning version is always also valid for the other planning versions if specific, planning-version-dependent data has not been maintained for them. When this method is executed, no database locks are set and evaluated, since the interface has highest priority. You can find information about classifying products here. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information.

B2

FUNCTIONALITY You can use this method to read products for certain selection criteria. HINTS There are the following options for selecting the products. Combinations of the alternatives are not possible or are ignored. Selection by entering the product GUID "ProductGuids" Selection using RANGES tables: The following combinations can be used for this: "ProductSelection" + "ModelSelection" (optional) + "BsgSelection" (optional) + "LocationSelection" (optional) + "LoctypeSelection" (optional) "ProductIntSelection" + "ModelSelection" (optional) + "BsgSelection" (optional) + "LocationIntSelection" (optional) + "LoctypeSelection" (optional) Selection using explicit keys: "ProductKey" "ProductIntKey" In addition to the three selection variants, you can use the "PlanningVersionSelection" parameter to restrict the planning version for which data is to be returned in the "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" parameters. If the parameter is empty, only planning-version-independent default values are returned. If the selection is made using internal keys ("ProductIntSelection", "LocationIntSelection", "ProductIntKey") or Guids ("ProductGuids"), the external keys are not filled in the return parameters. Only the internal keys are returned. If you want to determine the associated external key, you have read in the "ProductMapping" or "LocationMapping" parameter using the internal key and business system group. Note that this method can read data for products from different business system groups. There is no restriction to the business system group to which the logical system specified belongs ("LogicalSystem"). The classification of products is seen as a separate object. For more information, see here. In general, you are only recommended to read the parameters that are actually needed. For more information, see the documentation for the "ExcludeExportFlags" parameter. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information Using internal selection

B4


B8


B9

10

B10


M028 - FG RIDSECT APDCLNT001APDCLNT001APDCLNT001APDCLNT001

M028 - FOR RIDSECT APDCLNT001APDCLNT001

M028 - RM / PM RIDSECT APDCLNT001APDCLNT001APDCLNT001APDCLNT001APDCLNT001APDCLNT001

M027 - FG KIWIAPDCLNT001APDCLNT001APDCLNT001APDCLNT001APDCLNT001

M027 - FOR KIWIAPDCLNT001APDCLNT001APDCLNT001

M027 - RM / PM KIWIAPDCLNT001APDCLNT001APDCLNT001APDCLNT001APDCLNT001APDCLNT001

L044 - FGAPDCLNT001APDCLNT001APDCLNT001APDCLNT001

product_location

product_id product

Product GUID (Length 32) External Product Indicatorbapi10001matid_32 /sapapo/ext_matnr

char/ 32/ char/ 40/

45CF3ED23D966AE4E10000000A80314E AC0023045CF3EDF3D966AE4E10000000A80314E AC0003945CF3EEC3D966AE4E10000000A80314E AC0014645CF3EF93D966AE4E10000000A80314E AC00157

45D154B252AE40C6E10000000A80314E 01068145D154B652AE40C6E10000000A80314E 800045D154BA52AE40C6E10000000A80314E 01068045D154BE52AE40C6E10000000A80314E 8001

45D154C652AE40C6E10000000A80314E A0090445D154C252AE40C6E10000000A80314E A8000445D154CA52AE40C6E10000000A80314E A7000045D154CE52AE40C6E10000000A80314E A5000545D420CB20B9288FE10000000A80314E A70001

45CF40DC3D31680AE10000000A80314E AM0011045CF40E93D31680AE10000000A80314E AM0006045CF40F63D31680AE10000000A80314E AM0008045CF41033D31680AE10000000A80314E AM00090

45D5265026066BDEE10000000A80314E 1069045D5265426066BDEE10000000A80314E 1069145D5265826066BDEE10000000A80314E 10688

45D55BB058E235F4E10000000A80314E A7400045D55BA858E235F4E10000000A80314E A7400245D55BAC58E235F4E10000000A80314E A74003

C4

MEANING Transfer parameter for location-dependent product data. HINTS The fields "AbcIndicator", "ReplenishmentControl", "UomGroup", "SalesPriceCurrency", and "ConsRefProduct" are specific fields for the application F&R ("Forecast & Replenishment"). They are not used as standard. The field "SalesPrice" is converted into the client currency according to "SalesPriceCurrency" and then stored. If "SalesPriceCurrency" is empty, the client currency is used as the currency and the value is not converted. DEFAULT

D8


C9

32

D9

40

C10


D10


D11


45D9555D5313057DE10000000A80314E 90310645D955615313057DE10000000A80314E 90121645D955655313057DE10000000A80314E 90009745D955695313057DE10000000A80314E 903107

45D9556D5313057DE10000000A80314E 900045D955715313057DE10000000A80314E 9103

45D955755313057DE10000000A80314E RMP000345D955795313057DE10000000A80314E RMP004345D955815313057DE10000000A80314E CTC318045D955855313057DE10000000A80314E CTC318145D955895313057DE10000000A80314E CTC318945D9558D5313057DE10000000A80314E CTC3179

45D9747C71A73EA3E10000000A80314E 20034045D9748071A73EA3E10000000A80314E 20038045D9748471A73EA3E10000000A80314E 20111445D9748871A73EA3E10000000A80314E 20080945FF7334728E090AE10000000A80314E 0000000000000000000000000000000000215031

45D9748C71A73EA3E10000000A80314E 401345D9749071A73EA3E10000000A80314E 401445D9749471A73EA3E10000000A80314E 4008

45D9749871A73EA3E10000000A80314E 1031145D9749C71A73EA3E10000000A80314E 1030745D974A071A73EA3E10000000A80314E 1324845D974A471A73EA3E10000000A80314E 1324745D974A871A73EA3E10000000A80314E 1324145D974AC71A73EA3E10000000A80314E 13240

45CF3EDF3D966AE4E10000000A80314E AC0003945CF3ED23D966AE4E10000000A80314E AC0023045CF3EEC3D966AE4E10000000A80314E AC0014645CF3EF93D966AE4E10000000A80314E AC00157

product_int location_id location

Product ID Location GUID (Length 32) External Location ID/sapapo/matnr bapi10002locid_32 /sapapo/ext_locno


AC00230 45AEF358F2ED55BEE10000M026AC00039 45AEF358F2ED55BEE10000M026AC00146 45AEF358F2ED55BEE10000M026AC00157 45AEF358F2ED55BEE10000M026

0000000000000000000000000000000000010681 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000008000 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000010680 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000008001 45AEF358F2ED55BEE10000M026

A00904 45AEF358F2ED55BEE10000M026A80004 45AEF358F2ED55BEE10000M026A70000 45AEF358F2ED55BEE10000M026A50005 45AEF358F2ED55BEE10000M026A70001 45AEF358F2ED55BEE10000M026

AM00110 45AEF358F2ED55BEE10000M026AM00060 45AEF358F2ED55BEE10000M026AM00080 45AEF358F2ED55BEE10000M026AM00090 45AEF358F2ED55BEE10000M026

0000000000000000000000000000000000010690 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000010691 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000010688 45AEF358F2ED55BEE10000M026

A74000 45AEF358F2ED55BEE10000M026A74002 45AEF358F2ED55BEE10000M026A74003 45AEF358F2ED55BEE10000M026

E8


E9

40

F9

32

G9

20

E10


F10


G10


E11


G11


0000000000000000000000000000000000903106 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000901216 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000900097 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000903107 45AEFDAEFD790E82E1000M028

0000000000000000000000000000000000009000 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000009103 45AEFDAEFD790E82E1000M028

RMP0003 45AEFDAEFD790E82E1000M028RMP0043 45AEFDAEFD790E82E1000M028CTC3180 45AEFDAEFD790E82E1000M028CTC3181 45AEFDAEFD790E82E1000M028CTC3189 45AEFDAEFD790E82E1000M028CTC3179 45AEFDAEFD790E82E1000M028

0000000000000000000000000000000000200340 45AEFD93FD790E82E10000M0270000000000000000000000000000000000200380 45AEFD93FD790E82E10000M0270000000000000000000000000000000000201114 45AEFD93FD790E82E10000M0270000000000000000000000000000000000200809 45AEFD93FD790E82E10000M027BSGSLDE1 45AEFD93FD790E82E10000M027

0000000000000000000000000000000000004013 45AEFD93FD790E82E10000M0270000000000000000000000000000000000004014 45AEFD93FD790E82E10000M0270000000000000000000000000000000000004008 45AEFD93FD790E82E10000M027

0000000000000000000000000000000000010311 45AEFD93FD790E82E10000M0270000000000000000000000000000000000010307 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013248 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013247 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013241 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013240 45AEFD93FD790E82E10000M027

AC00039 45AEF15FF0D64280E10000L044AC00230 45AEF15FF0D64280E10000L044AC00146 45AEF15FF0D64280E10000L044AC00157 45AEF15FF0D64280E10000L044

loctype location_int production_planner snp_planner

Location Type Location Production Planner Supply Network Planner/sapapo/c_loctype /sapapo/locno /sapapo/planner_pps /sapapo/planner_snp


1001 M026 PH2 PH21001 M026 PH2 PH21001 M026 PH2 PH21001 M026 PH2 PH2


1001 M026 PH6 PH61001 M026 PH6 PH61001 M026 PH6 PH61001 M026 PH6 PH61001 M026 PH6 PH6


1001 M026 PH2 PH21001 M026 PH2 PH21001 M026 PH2 PH2


H6


J8

Valuetable: /SAPAPO/PLANNER

K8


H9

4

I9

20

J9

3

K9

3

H10


I10


J10

DEFINITION Planner responsible for the location product in Production Planning and Detailed Scheduling. DEPENDENCIES You maintain the planner in Customizing via Advanced Planner and Optimizer (APO) -> Supply Chain Planning -> Specify the Person (Planner) Responsible.

K10

DEFINITION Uses an alphanumeric name to indicate the planner responsible for the location product in the area of Supply Network Planning. DEPENDENCIES You can maintain the planner in Customizing via Advanced Planner and Optimizer (APO) -> Supply Chain Planning -> Define responsible administrator (planner).

I11



1001 M028 PH2 PH21001 M028 PH2 PH2

1001 M028 PH6 PH61001 M028 PH6 PH61001 M028 PH6 PH61001 M028 PH6 PH61001 M028 PH6 PH61001 M028 PH6 PH6

1001 M027 PH2 PH21001 M027 PH2 PH21001 M027 PH2 PH21001 M027 PH2 PH21001 M027 PH2 PH2


1001 M027 PH6 PH61001 M027 PH6 PH61001 M027 PH6 PH61001 M027 PH6 PH61001 M027 PH6 PH61001 M027 PH6 PH6

1002 L0441002 L0441002 L0441002 L044

demand_planner transportation_planner purchasing_planner vmi_planner

Demand Planner Transportation Planner Purchasing Planner ICH Planner/sapapo/planner_demand /sapapo/planner_trans /sapapo/planner_pur /sapapo/planner_vmi


L8


M8


N8


O8


L9

3

M9

3

N9

3

O9

3

L10

DEFINITION Uses an alphanumeric name to indicate the planner responsible for the location product in the area of Demand Planning. DEPENDENCIES You can maintain the planner in Customizing via Advanced Planner and Optimizer (APO) -> Supply Chain Planning -> Define responsible administrator (planner).

M10

DEFINITION An alphanumeric ID indicates the responible planner for the location product in the area of Transportation Planning DEPENDENCIES You can maintain the planner in Customizing via Advanced Planner and Optimizer (APO) -> Supply Chain Planning -> Define responsible administrator (planner).

smi_planner reference_product reference_product_bsg

SMI Planner Configurable Product Business System Group/sapapo/planner_smi /sapapo/stdpd /sapapo/logqs


P8


Q8


R8


P9

3

Q9

40

R9

8

Q10

DEFINITION Number that uniquely identifyies the configurable product.

R10


prd_alloc_proc

Product Allocations: Product Allocation Procedure/sapapo/kosch

char/ 18/

S8


S9

18

S10

DEFINITION The product allocation procedure determines how a product in limited supply is allocated to (sales) orders. The product allocation procedure can also be location-dependent (see location-dependent product allocation procedure) USE You enter the product allocation procedure in the product master record in APO or in a sequence of product allocation procedures. DEPENDENCIES In addition, different Customizing settings determine how product allocation is carried out: You can define several product allocation steps in a product allocation procedure. You assign a product allocation group to the product allocation step. The product allocation group determines the criteria that the system uses to choose a product allocation in the availability check. The consumption period determines the periods for the product allocation time series surrounding the checking date. The free product allocation quantities of these periods are then used in the confirmation invoice. The consumption periods are defined per product allocation group. You can assign several product allocation objects in the control for a product allocation step. Each object is valid for a period. The product allocation objects represent the reason for product allocation. The product allocation object is the first characteristic in the product allocation group. If you change the product allocation object, a different product allocation time series is used for the corresponding period in the check.

prd_alloc_proc_seq check_mode atp_group

Prod. Allocations: Sequence of Product Allocation Procedures Check Mode ATP Group/sapapo/kosch_grp /sapapo/atp_chmod /sapapo/mtvfp


T8


U8

Valuetable: /SAPAPO/ATP06

V8

Valuetable: /SAPAPO/ATP01

T9

18

U9

3

V9

2

T10

DEFINITION Via a sequence of product allocation procedures, several product allocation procedures are combined into a specific sequence. The sequence of product allocation procedures can also be location-dependent (see location-dependent product allocation procedure). USE The sequence of product allocation procedures determines several alternative product allocation procedures and their sequence for a product. The list of product allocation procedures is used for product allocation in the availability check. If the quantity cannot be fully confirmed in a product allocation procedure when checking, the system carries out product allocation for the remaining quantity in the next product allocation procedure in the sequence. The first product allocation procedure used is the product allocation procedure from the product master record. Every other procedure used comes from the sequence of product allocation procedures. If the product allocation procedure from the product master record appears in the list again, the system ignores it. NOTE You enter the sequence of product allocation procedures and the product allocation procedure in the product master record in APO. The sequence of product allocation procedures is only used to supplement the product allocation procedure. If a product allocation procedure has not been entered for the product, the system ignores the sequence of product allocation procedures and terminates product allocation. You can use a sequence of product allocation procedures, similar to the product allocation procedure, for several products. The range of products, for which a sequence of product allocation procedures is used, does not have to be covered with a range of products from the product allocation procedures.

U10

DEFINITION The check mode derived from the product master record and the business event determine the type and scope of the checks to be carried out. In addition, the check mode controls consumption using the forecast. The SD (R/3) uses the requirements class of the requirement as check mode. As of R/3 Plugin 2000.1, the requirements class (via the strategy group in the material master) is transferred to the location-specific APO product master (tab page ATP). No plausibility check takes place. Therefore, you should not enter any other check mode in the product master as the check mode in the product master must correspond to the requirements class from the R/3 System.

V10

DEFINITION The ATP group combines a group of settings for the product availability check and corresponds to the checking group in R/3. The checking group is transferred via the APO Core Interface as an ATP group to the location-specific APO product master (tab page ATP).

checking_horizon checking_horizon_calendar

ATP: Checking Horizon in Days ATP: Checking Horizon Calendar/sapapo/chkhor /sapapo/chkhorcal

numc/ 3/ char/ 10/

X8

Valuetable: TTSTR

W9

3

X9

10

W10

DEFINITION Defines a time interval (checking date + period) in which a product availability check can be carried out. If the requirements date lies within this time interval, the check is carried out. Requirements that lie beyond the checking horizon are not checked; that is, the system confirms the requirements in full. use You can display the replenishment lead time , for example, using the checking horizon. If you want to include the checking horizon in the product availability check, you must set the corresponding indicator in Customizing for the product availability check. note If you do not use the calendar for the checking horizon, the checking horizon is calculated in days. The checking horizon is calculated in work days in accordance with the calendar, if you use the calendar for the checking horizon.

X10

DEFINITION The calendar for the checking horizon corresponds to a planning calendar (time stream) that you have created in Customizing for master data. Use The calendar for the checking horizon is used to calculate the end of the checking horizon. The checking horizon is calculated in work days.

recreate_receipts_horizon display_uom

ATP: Horizon for Recreating Receipts in Calendar Days ATP: Display Unit of Measure/sapapo/rcrrcphor /sapapo/diuom

numc/ 3/ unit/ 3/

Z8


Y9

3

Z9

3

Y10

DEFINITION Defines a time period behind which receipt elements, created via Capable-To-Promise (CTP) or via a conversion of the ATP tree structure (after a multilevel ATP check) in the order network of liveCache, are deleted by the system before a new ATP check takes place. The time period consists of check date (today's date) and calendar days that you specify in the horizon for re-creating receipts. use You have already performed CTP processing or a conversion of the ATP tree structure (after a multilevel ATP check) and change the sales order in SAP R/3 (SD), for example. If the requirements date (material availability date) is later than the end of the horizon, then the system attempts to delete the receipt elements created in a previous check and to create them within a new ATP check. dependencies You set the Rcrt.rcpts indicator in the check instructions. In Customizing for the Advanced Planner and Optimizer (APO) choose Global Availability Check (Global ATP Check) -> General Settings -> Maintain Check Instructions. Creating receipt elements again within CTP processing or a conversion of the ATP tree structure (after a multilevel ATP check) is only permitted for make-to-order production. In SAP R/3, make-to-order production can be controlled via the requirements type. The requirements type is determined, for example, via the MRP group and strategy group in the material master. The receipt elements must have a status that allows deletion.

display_uom_iso customer_product snp_checking_horizon

ISO code for unit of measurement Customer Product Number SNP: Checking Horizon in Daysisocd_unit /sapapo/kdmat /sapapo/snpchkhor

char/ 3/ char/ 40/ numc/ 3/

AA8

Valuetable: T006I

AA9

3

AB9

40

AC9

3

AA10


AB10

DEFINITION Specifies the material number which the customer uses for this product. This information is used in vendor-managed inventory (VMI). The customer submits inventory data and POS data via EDI through an IDOC. The system uses this field to find the match between the customer's material number, as specified in the IDOC, and the APO product number.

AC10

DEFINITION USE The SNP checking horizon is used in deployment to calculate the quantity available for distribution to the demand locations (available-to-deploy (ATD) quantity). It limits the quantity that is available within the push deployment horizon. If you specify an SNP checking horizon, deployment calculates the ATD quantity for a period within the SNP checking horizon by adding the ATD receipts for the current period and the past periods and subtracting all ATD issues within the SNP checking horizon. If you do not specify an SNP checking horizon, or the period in question lies outside the SNP checking horizon, deployment adds the ATD receipts of the current period and the past periods and subtracts the ATD issues for these periods. Deployment takes only ATD receipts and issues within the push deployment horizon into account. DEPENDENCIES You can define the SNP checking horizon for the deployment optimizer both in the location product master (on the SNP2 tab page) and in the SNP deployment optimizer profile (on the Deployment Parameters tab page). If you want the deployment optimizer to take into account the value defined in the location product master, you have to enter a value there of > 0 and set the Horizons from Product Master/ Profile indicator in the deployment optimizer profile. If you do not do this, the system uses the value you defined in the deployment optimizer profile. EXAMPLE The following example illustrates the advantages of an SNP checking horizon: Period,,ATD quantity,,ATD issue 1,,1000,,0,, 2,,1000,,0 3,,500,,500 If you have not specifed an SNP checking horizon, deployment can distribute the entire available quantity of 1000 pieces in the first period. However, this would lead to a shortage of 500 pieces in the third period. With a sufficiently large SNP checking horizon, the available quantity would already be reduced in the first period by the issue of 500 pieces from the third period. This would prevent a shortage resulting from deployment distributing excessive quantities in the first two periods. The following example illustrates the disadvantages of an SNP checking horizon: Period,,1,,2 ATD receipt:,,100,,100 ATD issue:,,0,,100,,,,,,,,,,,,,, ATD quantity with checking horizon:,,0,,100 ATD quantity without checking horizon:,,100,,100 Planned distribution demand:,,100,,0 Deployment can only distribute a minimum of the available quantity within the SNP checking horizon. This can result in deployment not confirming an SNP stock transfer at the earliest possible point in time. The planned distribution demand could not be confirmed by deployment until the second period although a sufficient ATD quantity was already available in the first period.

vmi_purchasing_group purchasing_group

VMI Purchasing Group Purchasing Group/sapapo/vegrp /sapapo/ekgrp

char/ 20/ char/ 3/

AD9

20

AE9

3

AD10

DEFINITION Indicates the identifier for the buyer or group of buyers responsible for purchasing tasks for the VMI product. The VMI purchasing group is defined in the product master, SNP 2 tab. This information is used by the TLB to group products together during load building calculations according to the VMI customer purchasing group assigned to individual products. Multiple products could have the same VMI purchasing group. Orders from more than one VMI purchasing group could be transferred to the demand source in the same transport load then diverted to the appropriate customer groups. Product master

AE10

DEFINITION Key for a buyer or a group of buyers that are responsible for certain purchasing tasks. VERWENDUNG The group of buyers is responsible internally for the procurement of a material or a class of materials, externally responsible for contact with suppliers.

shelf_life_flag shelf_life

Use Location-Dependent Shelf Life of Product when Planning Location-Dependent Shelf Life/sapapo/shelf_life_loc_flag /sapapo/shelf_life_dur_l

char/ 1/ dec/ 11/ 0

AF6

X Yes No

AG8


AF9

1

AG9

10

maturation_time req_min_shelf_life

Location-Dependent Maturation Time Minimum Shelf Life Required: Location-Dependent/sapapo/maturity_dur_l /sapapo/shelf_life_req_min_l

dec/ 11/ 0 dec/ 11/ 0

AH8


AI8


AH9

10

AI9

10

req_max_shelf_life forecast_error_demand

Maximum Shelf Life Required: Location-Dependent Relative Demand Forecast Error in %/sapapo/shelf_life_req_max_l /sapapo/fedem

dec/ 11/ 0 dec/ 4/ 1

AJ8


AJ9

10

AK9

5

AK10

DEFINITION Percentage that depicts the mean deviation relationship between the forecast demand and the actual demand at demand forecast level. The lower the percentage, the more accurate the demand forecast (that is, it is more likely to correspond to actual demands). USE The extended safety stock planning methods in Supply Network Planning (SNP) use the relative forecast error of the demand as information about the "uncertainty" of demand forecasts. If the relative forecast error is large, you will need a larger amount of safety stock to achieve a predefined service level. You can enter the demand forecast error directly in this field or allow the system to calculate the forecast error using historical data. We recommend that you enter the information directly in the following instances: There is no historical data (because the product is new, for instance) There is so little historical data that it is not possible to calculate a statistically significant forecast error The forecast error is considered to be almost constant You can specify values of between 0.0% and 999.9%. If the value is 0.0%, the system uses historical data to determine the relative forecast error of the demand. If you do not enter a value, the system assumes that the forecast error is 0.0%. If you enter a value larger than 0.0%, safety stock planning in SNP uses this value as a relative forecast error of the demand. The system does not take historical data into account in this instance. DEPENDENCIES The system only takes into account the value specified in this field if you have chosen one of the extended safety stock methods (AS, AT, BS , or BT) from the Safety Stock Method field. EXAMPLE

forecast_error_rlt planning_group

Relative Forecast Error of Replenishment Lead Time in % Planning Group/sapapo/ferld /sapapo/rrp_selection_group

dec/ 4/ 1 char/ 2/

AM8

Valuetable: /SAPAPO/RRP_GRP

AL9

5

AM9

2

AL10

DEFINITION Percentage that depicts the mean deviation relationship between the replenishment lead time (RLT) that was forecast and the real RLT at RLT forecast level. The lower the percentage, the smaller the deviation between the forecast RLT and the actual RLT. USE The extended safety stock planning methods in Supply Network Planning (SNP) use the relative forecast error of the RLT as information about "uncertainty" of the RLT forecast. If the relative forecast error is large, you will need a larger amount of safety stock to achieve a predefined service level. You can enter the RLT forecast error directly in this field or allow the system to calculate the forecast error using historical data. We recommend that you enter the information directly in the following instances: There is no historical data (because the product is new, for instance) There is so little historical data that it is not possible to calculate a statistically significant forecast error The forecast error is considered to be almost constant You can specify values of between 0.0% and 999.9%. If the value is 0.0%, the system uses historical data to determine the relative forecast error of the RLT. If you do not enter a value, the system assumes that the forecast error is 0.0%. If you enter a value that is larger than 0.0%, safety stock planning in SNP uses this value as the relative RLT forecast error. The system does not take historical data into account in this instance. DEPENDENCIES The system only takes into account the value entered in this field if you chose one of the extended safety stock methods AS, AT, BS, or BT from the Safety Stock Method field. EXAMPLE

AM10

DEFINITION Planning group USE DEPENDENCIES EXAMPLE

conversion_rule production_uom production_uom_iso

Conversion Rule Display Production Unit ISO code for unit of measurement/sapapo/prof_exec_check /sapapo/frtme isocd_unit

char/ 12/ unit/ 3/ char/ 3/

AO8


AP8

Valuetable: T006I

AN9

12

AO9

3

AP9

3

AN10

definition Specifies which checks the system executes for the conversion of planned orders and purchase requisitions to production orders or purchase orders. use The system executes the checks in the SAP APO system, if the conversion indicator is set for an order if you transfer an order to the SAP R/3 system and convert it, with the conversion indicator set. If one of the checks leads to an error, this can have the following consequences: The conversion indicator cannot be set. The order cannot be transferred to the R/3 system and converted. dependencies You can define according to specific roles, whether a user is allowed to set the conversion indicator interactively for an order or execute the conversion of the order, if a check results in an error. For more information, see Role-specific overriding of the check. The system uses the conversion rule that you have assigned to the relevant location product, or - if you have not assigned a conversion rule to the location product - it uses the conversion rule that you have specified in the customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Default Values .

AP10


gr_hndl_cap_cons

Handling Capacity Consumption in Unit of Measure (Gds Rcpt)/sapapo/snpconhap

quan/ 13/ 3

AQ8

Reference Table: BAPI10001LOCPRD2 Reference Field: GR_HNDL_CAP_CONS_UOM

AQ9

17

AQ10

Used by the Heuristic and Optimizer to calculate how much handling resource capacity is consumed by the product for a particular plan. If the handling resource can handle 1000 liters per day, and you define the handling capacity consumption as 10 liters per piece, the maximum rate is 100 pieces per day.

gr_hndl_cap_cons_uom gr_hndl_cap_cons_uom_iso

Unit of Measure: Handling Capacity in Goods Receipt ISO code for unit of measurement/sapapo/hunit isocd_unit

unit/ 3/ char/ 3/

AR8


AS8

Valuetable: T006I

AR9

3

AS9

3

AS10


gi_hndl_cap_cons

Handling Capacity Consumption in Unit of Measure (Gds Issue)/sapapo/snpconhap_out

quan/ 13/ 3

AT8

Reference Table: BAPI10001LOCPRD2 Reference Field: GI_HNDL_CAP_CONS_UOM

AT9

17

AT10

Used by the Heuristic and Optimizer to calculate how much handling resource capacity is consumed by the product for a particular plan. If the handling resource can handle 1000 liters per day, and you define the handling capacity consumption as 10 liters per piece, the maximum rate is 100 pieces per day.

gi_hndl_cap_cons_uom gi_hndl_cap_cons_uom_iso

Unit of Measure: Handling Capacity in Goods Issue ISO code for unit of measurement/sapapo/hunit_out isocd_unit

unit/ 3/ char/ 3/

AU8


AV8

Valuetable: T006I

AU9

3

AV9

3

AV10


storage_cap_cons storage_cap_cons_uom

Consumption of Storage Capacity per Unit of Material Unit of Measure/sapapo/snpconinp /sapapo/unit

quan/ 13/ 3 unit/ 3/

AW8

Reference Table: BAPI10001LOCPRD2 Reference Field: STORAGE_CAP_CONS_UOM

AX8


AW9

17

AX9

3

AW10

Used by the Heuristic and Optimizer to calculate how much storage capacity is consumed by the product for a particular plan. If the storage resource capacity is 1000 cubic meters, and you define the storage consumption as 5 cubic meters per piece, that means you can store a maximum of 200 pieces.

storage_cap_cons_uom_iso pick_pack_time transportation_lead_time

ISO code for unit of measurement Pick/Pack Time Transportation Lead Timeisocd_unit /sapapo/piprt /sapapo/tlprt

char/ 3/ dec/ 11/ 0 dec/ 11/ 0

AY8

Valuetable: T006I

AZ8


BA8


AY9

3

AZ9

10

BA9

10

AY10


AZ10

DEFINITION The time needed to assign a product to a delivery, to pick it, and to pack it. USE The pick/pack time is used in SAP APO for VMI orders to calculate the loading date from the requirement date or material availability date. If you have not maintained a pick and pack time in the product master, the loading date is the same as the requirement date. DEPENDENCIES The pick/pack time is only taken into account for scheduling if you activated extended VMI scheduling in VMI Customizing. The pick/pack time is not be permitted to be longer than the goods issue processing time. EXAMPLE

BA10

DEFINITION The time needed to organize transportation. USE The transportation lead time is used in SAP APO for VMI orders to calculate the transportation planning date starting from the loading date. If you have not maintained the transportation lead time in the product master, the transportation lead time is the same as the loading date. DEPENDENCIES The transportation lead time is taken into account for scheduling if extended VMI scheduling has been activated in VMI Customizing. EXAMPLE

prom_always_use_order_flag prom_load_together_flag

Do not Cover Sales Deal with VMI Customer Stocks Normal and Sales Deal Deliveries Deliverable/sapapo/pro_ord /sapapo/pro_ltp

char/ 1/ char/ 1/

BB6

X Yes No

BC6

X Yes No

BB9

1

BC9

1

out_of_stock_threshold loading_group dead_pile_flag

Alert Threshold for Out-of-Stock Loading Group Indicator: Non-Palletable/sapapo/os_limit /sapapo/ladgr /sapapo/deadpile

quan/ 13/ 3 char/ 4/ char/ 1/

BF6

X Yes No

BD8

Reference Table: BAPI10001PRD2 Reference Field: BASE_UOM

BD9

17

BE9

4

BF9

1

BD10

DEFINITION Indicates the threshold value for an out-of-stock (stock shortfall) alert. USE If you enter a threshold value for the stock here, the system will issue an alert if the stock level falls below this value. DEPENDENCIES EXAMPLE

BE10

DEFINITION Groups the products for which the same requirements for loading are valid. USE The loading group can be used in Scheduling to determine times and to calculate dates. The Transport Load Builder (TLB) in the Inventory Collaboration Hub (ICH) or in Supply Network Planning (SNP) considers the loading group when it uses the straight loading procedure. In this procedure, the system tries to assemble shipments using the same products or products from the same loading group.

BF10

DEFINITION Indicates whether a location product can be stacked on pallets. USE The Transport Load Builder (TLB) in the Inventory Collaboration Hub (ICH) and Supply Network Planning (SNP) takes the indicator into account when calculating the pallets to be used for a shipment. DEPENDENCIES EXAMPLE

gi_sync_posting_flag abc_indicator replenishment_control

Synchronous Posting of Goods Issue ABC indicator Replenishment Type of Product/sapapo/ppc_gmsync /sapapo/maabc /sapapo/rpstatus


BG6

X Yes No

BI6

00 Inactive for Automatic Replenishment 01 Inactive for Automatic Replenishment Due to Cross Docking 09 Auto. Replen. w. Manual Target Stock + Manual Reorder Point 10 Auto. Replen. w. Manual Target Stock + Dynamic Reorder Point 11 Automatic Replen. w. Dyn. Target Stock + Dyn. Reorder Point 12 Manual Replenishment Only 13 Replenishment is Manual (But Automatic Also Possible)

BG9

1

BH9

1

BI9

2

BG10

DEFINITION Specifies whether the goods issue of this component is to be posted synchronously or asynchronously in the R/3 System. USE You set this indicator if the posting of the goods issue for this component is to be carried out synchronously (i.e. immediately the data is transferred from the APO system to R/3). Otherwise, the posting is asynchronous, i.e. the data is initially written to a buffer in the database. The processing and posting of the data is not carried out until later via a report. DEPENDENCIES EXAMPLE

uom_group po_processing_time

Unit of Measure Group Purchase Order Processing Time Required by Purchasing Dept./sapapo/measgrbuy /sapapo/purtime

char/ 4/ dec/ 11/ 0

BK8


BJ9

4

BK9

10

target_stock_on_hand sales_price sales_price_currency

Minimum Target Stock on Hand for a Product Sales Price of Product Currency Key/sapapo/minstock /sapapo/salesprice waers

fltp/ 16/ dec/ 13/ 3 cuky/ 5/

BL8

Reference Table: BAPI10001PRD2 Reference Field: BASE_UOM

BN8

Valuetable: TCURC

BL9

22

BM9

17

BN9

5

BN10

DEFINITION Currency key for amounts in the system.

sales_price_currency_iso consumption_ref_product consumption_ref_product_bsg

ISO currency code External Product Indicator Business System Groupisocd /sapapo/ext_matnr /sapapo/logqs


BP8


BQ8


BO9

3

BP9

40

BQ9

8

BO10

DEFINITION Currency key (standard worldwide). WHAT_TO_DO Enter the ISO code If you do not already use the global standard currency key as the currency key If you use the EDI application. Here the ISO code is used for exchanging information.

BP10


BQ10


attribute_1 attribute_2 attribute_3 attribute_4

Character field of length 40 30 Characters Char 20 Character Field Length = 10char40 char30 char20 char10


BR9

40

BS9

30

BT9

20

BU9

10

attribute_5 use_of_turn_stock_flag

Character Field Length = 10 Use of Baseline Stock for Promotionschar10 /sapapo/usetp

char/ 10/ char/ 1/

BW6

Use of Baseline Stock for Promotions not Allowed X Use Baseline Stock for Promotions and Round Separately R Use Baseline Stock for Promotions and Round Together

BV9

10

BW9

1

BW10

DEFINITION Indicates whether or not the use of baseline stock for promotions is allowed. USE The indicator is used by the Transport Load Builder. DEPENDENCIES EXAMPLE

turn_stock_prom_mix_flag max_coverage_upsize_flag

Separate Transportation of Baseline and Promotion Shipment Upsizing/sapapo/mixtp /sapapo/maxcoverup

char/ 1/ char/ 1/

BX6

Mixing of Baseline/Promotion in One Shipment Allowed X Mixing of Baseline/Promotion in One Shipment not Allowed

BY6

X Shipment Upsizing Over Maximum Coverage Period Allowed N No Shipment Upsizing Allowed Shipment Upsizing Up To Maximum Coverage Period Allowed

BX9

1

BY9

1

BX10

DEFINITION Indicates whether or not mixing of baseline and promotion quantities in the same means of transport is allowed. USE The indicator is used by the Transport Load Builder. DEPENDENCIES EXAMPLE

BY10

DEFINITION Indicates for a location product whether a shipment upsizing is generally allowed and is also possible beyond the maximum coverage period defined in the adjacent field. USE The shipment upsizing procedure is used by the Transport Load Builder TLB in the Inventory Collaboration Hub (ICH) and in Supply Network Planning (SNP) to achieve complete shipments and avoid residual quantities. DEPENDENCIES You can define the shipment upsizing procedure even more precisely in Customizing for the ICH and for SNP under Make TLB Basic Settings. EXAMPLE

max_coverage_period handling_unit_group vmi_prd_alloc_proc

Maximum Coverage Period in Days Handling Unit Group Allocation: VMI Allocation Procedure/sapapo/maxcover /sapapo/hugrp /sapapo/vmikosch

int1/ 3/ char/ 4/ char/ 18/

CB8


BZ9

3

CA9

4

CB9

18

BZ10

DEFINITION Indicates the maximum coverage period per location product in days. USE The maximum coverage period is taken into account by the Transport Load Builder (TLB) in the Inventory Collaboration Hub (ICH) and in Supply Network Planning (SNP) if the system carries out a shipment upsizing. With this procedure, the TLB brings forward deployment stock transfers from the pull-in horizon to achieve complete shipments and avoid residual quantities. With the coverage period, you can specify for a location product that the TLB is to bring forward only as many deployment stock transfers for the product as are necessary to cover the requirement for this period. DEPENDENCIES In the adjacent field Shipm. Upsizing, you can specify whether shipment upsizing is generally allowed for the product and is also possible beyond the coverage period. EXAMPLE If you have specified a coverage period of three days, the TLB will bring forward no more than the number of deployment stock transfers for a product that will cover requirements for three days. If the TLB needs further deployment stock transfers to create a complete shipment, it will bring forward the deployment stock transfers for other products.

CA10

DEFINITION Indicates a group of location products that can be packed together in the same handling unit (HU). USE Location products that are assigned to different HU groups must not be packed in the same handling unit. All location products belonging to the same HU group may be packed together in the same handling unit. The HU group is freely definable. The HU group is also taken into account by the Transport Load Builder (TLB) in the Inventory Collaboration Hub (ICH) and in Supply Network Planning (SNP). However, the SNP TLB does not use handling units. Location products that are assigned to different HU groups may not be loaded together on the same pallet in the SNP TLB. DEPENDENCIES EXAMPLE In the case of packing on pallets, all location products belonging to the HU group "non-liquid detergents" may be packed on the same pallet - and only these. Whether different products with the same HU group may be packed on a pallet in the SNP TLB also depends on the settings you have made in Customizing for SNP under Maintain Global SNP Settings.

CB10

DEFINITION The allocation procedure specifies how a product of which only a limited quantity is available is to be allocated to (sales) orders. The allocation procedure can also be location-dependent (selection: see location-dependent allocation procedure). USE You enter the allocation procedure on the APO data screen of the APO product master record or in an allocation procedure sequence. DEPENDENCIES Furthermore, various Customizing settings determine how the allocation is to be made: You can define several allocation steps in an allocation procedure. You assign an allocation group to an allocation step. The allocation group defines the criteria by which an allocation is selected in the availability check. The consumption period determines the periods of the allocation time series around the check date, whose free allocation quantity may be used for the confirmation calculation. The consumption period is defined per allocation group. In the allocation control for an allocation step, you can assign several allocation objects. Each of these objects is valid for a period. The allocation objects represent the reason for the allocation. The allocation object is the first characteristic in the allocation group. Through a change in the allocation object, a different allocation time series is used for the relevant period in the check.

vmi_prd_alloc_proc_seq replenishment_lead_time_shift

Allocation: VMI Allocation Procedure Sequence Replenishment Lead Time Shift/sapapo/vmikosch_grp /sapapo/leadtimeshift

char/ 18/ numc/ 2/

CC8


CC9

18

CD9

2

CC10

DEFINITION An allocation procedure sequence groups together several allocation procedures in a certain order. The allocation procedure sequence can also be location-dependent (selection: see location-dependent allocation procedure). USE The allocation procedure sequence determines several alternative allocation procedures and their sequence for a product. The list of allocation procedures is used for during allocation in the availability check. If the quantity cannot be completely confirmed in an allocation procedure at the time of the check, the allocation is carried out for the residual quantity in the next allocation procedure of the sequence. The first allocation procedure to be used is the allocation procedure from the product master. Each further procedure comes from the allocation procedure sequence. If the allocation procedure from the product reoccurs in the list it is ignored. NOTE The allocation procedure sequence is entered on the APO data screen in the APO product master alongside the allocation procedure. The allocation procedure sequence serves as a supplement to the allocation procedure only. If no procedure has been entered for the product, the allocation procedure sequence is ignored. The allocation is then not carried out. Like the allocation procedure, an allocation procedure sequence can be used for several products. The range of products for which an allocation procedure sequence is used need not correspond to that of an allocation procedure.

capital_tie_up_profile frp_error_treatment_profile replenishment_profile

Capital Tie-Up Profile F&R Profile for Handling FRP Errors in F&R Replenishment Profile F&R/sapapo/procl /sapapo/proexcp /sapapo/prorepl


CE9

10

CF9

10

CG9

10

forecast_profile listing_status seasonal_flag release_period stock_multiple

Forecast Profile F&R Listing Status Season Indicator Time of Release Stock Multiple/sapapo/profcst /sapapo/listingstatus /sapapo/seasonflag /sapapo/reltime /sapapo/stockmultiple

char/ 10/ numc/ 1/ char/ 1/ dec/ 11/ 0 fltp/ 16/

CI6

0 Not Listed 1 Listed

CJ6


CK8


CH9

10

CI9

1

CJ9

1

CK9

10

CL9

22

target_stock consumption_ref_valid_to consumption_ref_factor

Target Stock Consumption Reference: Valid To Consumption Reference: Factor/sapapo/targetstock /sapapo/consrefvalto /sapapo/consreffac

fltp/ 16/ dec/ 15/ 0 dec/ 13/ 3

CM9

22

CN9

19

CO9

17

consumption_ref_location consumption_ref_loctype consumption_ref_location_bsg

External Location ID Location Type Business System Group/sapapo/ext_locno /sapapo/c_loctype /sapapo/logqs


CQ6


CR8


CP9

20

CQ9

4

CR9

8

CP10


CQ10


CR10


selling_class sourcing_control atd_issue_qty_cat_group

Selling Class Sourcing Control Category Group for ATD Quantity (Issues)/sapapo/sellclass /sapapo/bwscl /sapapo/mat_atddm


CS9

1

CT9

1

CU9

3

CU10

USE This field is relevant to Deployment and the Transport Load Builder (TLB) in Supply Network Planning (SNP). With the category group for the ATD issue, you specify which order categories contribute to the reduction of the available-to-deploy quantity (ATD quantity) or the quantity available for building transport loads (for example, BM = sales orders). DEPENDENCIES You can specify this field in both the location product master and the location master. When Deployment is carried out or the TLB is executed, the system first checks whether the category group has been specified for the location product. If not, the system checks the entry at location level. If no category group has been defined for the location either, the system uses the standard category group ATI. You define the category group in Customizing for SNP under Maintain Category Groups. EXAMPLE

atd_receipts_qty_cat_group sfty_stk_calculation_flag

Category Group for ATD Quantity (Receipts) Parameter-Dependent ATP Safety Stock/sapapo/mat_atdsp /sapapo/pssflag

char/ 3/ char/ 1/

CW6


CV9

3

CW9

1

CV10

DEFINITION USE This field is relevant to Deployment and the Transport Load Builder (TLB) in Supply Network Planning(SNP). With the category group for the ATD receipt, you specify which order categories contribute to the increase of the available-to-deploy quantity (ATD quantity) or the quantity available for building transport loads (for example, EE = SNP planned orders). DEPENDENCIES You can specify this field in both the location product master and the location master. When Deployment is carried out or the TLB is executed, the system first checks whether the category group has been specified for the location product. If not, the system checks the entry at location level. If no category group has been defined for the location either, the system uses the standard category group ATR. You define the category group in Customizing for SNP under Maintain Category Groups. EXAMPLE

CW10

DEFINITION Enables calculation of the parameter-dependent ATP safety stock (PASS) for this location product. USE If you set this indicator, the system calculates and protects the PASS quantity during an availability check. DEPENDENCIES If you set this indicator, all of the following conditions must be met: On the tab page lot size in the location-dependent product master you have entered a safety stock. You have executed a forecast run in time series data management of Demand Planning, so that a forecasted monthly demand exists. In Demand Planning, you have stored the following percentages : percentage of forecasted monthly demand percentage of safety stock In the OLTP system you have selected a value for the PASS parameter which enables PASS calculation. In the Customizing of the product availability check, system administration has ensured that the category safety stock (CB) is not contained in the scope of check of the availability check. For more information, see the Implementation Guide (IMG) under Advanced Planning and Optimization -> Global Available-to- Promise (Global ATP) -> Product Availability Check -> Maintain Check Control. In the Customizing of the product availability check, system administration has defined the settings for the PASS. For more information, see the IMG Advanced Planning and Optimization -> Global Available-to-Promise (Global ATP) -> Product Availability Check -> Maintain Settings for PASS. EXAMPLE

product_location_version

tlb_cost_profile product_id product

TLB Cost Profile Product GUID (Length 32) External Product Indicator/sapapo/costprof_tlb bapi10001matid_32 /sapapo/ext_matnr


45CF3ED23D966AE4E10000000A80314E AC0023045CF3EDF3D966AE4E10000000A80314E AC0003945CF3EEC3D966AE4E10000000A80314E AC0014645CF3EF93D966AE4E10000000A80314E AC00157

45D154B252AE40C6E10000000A80314E 01068145D154B652AE40C6E10000000A80314E 800045D154BA52AE40C6E10000000A80314E 01068045D154BE52AE40C6E10000000A80314E 8001

45D154C652AE40C6E10000000A80314E A0090445D154C252AE40C6E10000000A80314E A8000445D154CA52AE40C6E10000000A80314E A7000045D154CE52AE40C6E10000000A80314E A5000545D420CB20B9288FE10000000A80314E A70001

45CF40DC3D31680AE10000000A80314E AM0011045CF40E93D31680AE10000000A80314E AM0006045CF40F63D31680AE10000000A80314E AM0008045CF41033D31680AE10000000A80314E AM00090

45D5265026066BDEE10000000A80314E 1069045D5265426066BDEE10000000A80314E 1069145D5265826066BDEE10000000A80314E 10688

45D55BB058E235F4E10000000A80314E A7400045D55BA858E235F4E10000000A80314E A7400245D55BAC58E235F4E10000000A80314E A74003

CY4

MEANING Transfer parameter for location-dependent and version-dependent product data. HINTS Note that it is currently possible to work with a planning version during a method call only. If several different planning versions are specified in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority", processing is terminated and an error message is issued. If the data entered in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" is planning-version-independent, the "PlanningVersion" field must be empty or contain the value "000". It is not possible to set planning-version-dependent data for the active planning version only ("000"). The data for the active planning version is always also valid for the other planning versions if specific, planning-version-dependent data has not been maintained for them. DEFAULT

CZ8


CX9

10

CY9

32

CZ9

40

CY10


CZ10


CZ11


45D9555D5313057DE10000000A80314E 90310645D955615313057DE10000000A80314E 90121645D955655313057DE10000000A80314E 90009745D955695313057DE10000000A80314E 903107

45D9556D5313057DE10000000A80314E 900045D955715313057DE10000000A80314E 9103

45D955755313057DE10000000A80314E RMP000345D955795313057DE10000000A80314E RMP004345D955815313057DE10000000A80314E CTC318045D955855313057DE10000000A80314E CTC318145D955895313057DE10000000A80314E CTC318945D9558D5313057DE10000000A80314E CTC3179

45D9747C71A73EA3E10000000A80314E 20034045D9748071A73EA3E10000000A80314E 20038045D9748471A73EA3E10000000A80314E 20111445D9748871A73EA3E10000000A80314E 20080945FF7334728E090AE10000000A80314E 0000000000000000000000

45D9748C71A73EA3E10000000A80314E 401345D9749071A73EA3E10000000A80314E 401445D9749471A73EA3E10000000A80314E 4008

45D9749871A73EA3E10000000A80314E 1031145D9749C71A73EA3E10000000A80314E 1030745D974A071A73EA3E10000000A80314E 1324845D974A471A73EA3E10000000A80314E 1324745D974A871A73EA3E10000000A80314E 1324145D974AC71A73EA3E10000000A80314E 13240

45CF3EDF3D966AE4E10000000A80314E AC0003945CF3ED23D966AE4E10000000A80314E AC0023045CF3EEC3D966AE4E10000000A80314E AC0014645CF3EF93D966AE4E10000000A80314E AC00157

product_int location_id location

Product ID Location GUID (Length 32) External Location ID/sapapo/matnr bapi10002locid_32 /sapapo/ext_locno


AC00230 45AEF358F2ED55BEE10000M026AC00039 45AEF358F2ED55BEE10000M026AC00146 45AEF358F2ED55BEE10000M026AC00157 45AEF358F2ED55BEE10000M026

0000000000000000000000000000000000010681 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000008000 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000010680 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000008001 45AEF358F2ED55BEE10000M026

A00904 45AEF358F2ED55BEE10000M026A80004 45AEF358F2ED55BEE10000M026A70000 45AEF358F2ED55BEE10000M026A50005 45AEF358F2ED55BEE10000M026A70001 45AEF358F2ED55BEE10000M026

AM00110 45AEF358F2ED55BEE10000M026AM00060 45AEF358F2ED55BEE10000M026AM00080 45AEF358F2ED55BEE10000M026AM00090 45AEF358F2ED55BEE10000M026

0000000000000000000000000000000000010690 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000010691 45AEF358F2ED55BEE10000M0260000000000000000000000000000000000010688 45AEF358F2ED55BEE10000M026

A74000 45AEF358F2ED55BEE10000M026A74002 45AEF358F2ED55BEE10000M026A74003 45AEF358F2ED55BEE10000M026

DA8


DA9

40

DB9

32

DC9

20

DA10


DB10


DC10


DA11


DC11


0000000000000000000000000000000000903106 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000901216 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000900097 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000903107 45AEFDAEFD790E82E1000M028

0000000000000000000000000000000000009000 45AEFDAEFD790E82E1000M0280000000000000000000000000000000000009103 45AEFDAEFD790E82E1000M028

RMP0003 45AEFDAEFD790E82E1000M028RMP0043 45AEFDAEFD790E82E1000M028CTC3180 45AEFDAEFD790E82E1000M028CTC3181 45AEFDAEFD790E82E1000M028CTC3189 45AEFDAEFD790E82E1000M028CTC3179 45AEFDAEFD790E82E1000M028

0000000000000000000000000000000000200340 45AEFD93FD790E82E10000M0270000000000000000000000000000000000200380 45AEFD93FD790E82E10000M0270000000000000000000000000000000000201114 45AEFD93FD790E82E10000M0270000000000000000000000000000000000200809 45AEFD93FD790E82E10000M027BSGSLDE1 45AEFD93FD790E82E10000M027

0000000000000000000000000000000000004013 45AEFD93FD790E82E10000M0270000000000000000000000000000000000004014 45AEFD93FD790E82E10000M0270000000000000000000000000000000000004008 45AEFD93FD790E82E10000M027

0000000000000000000000000000000000010311 45AEFD93FD790E82E10000M0270000000000000000000000000000000000010307 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013248 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013247 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013241 45AEFD93FD790E82E10000M0270000000000000000000000000000000000013240 45AEFD93FD790E82E10000M027

AC00039 45AEF15FF0D64280E10000L044AC00230 45AEF15FF0D64280E10000L044AC00146 45AEF15FF0D64280E10000L044AC00157 45AEF15FF0D64280E10000L044

loctype location_int planning_version demand_profile

Location Type Location Planning Version Supply Network Planning: External Demand Profile/sapapo/c_loctype /sapapo/locno /sapapo/vrsioex /sapapo/snpdprex


1001 M026 0001001 M026 0001001 M026 0001001 M026 000

1001 M026 0001001 M026 0001001 M026 0001001 M026 000

1001 M026 0001001 M026 0001001 M026 0001001 M026 0001001 M026 000

1001 M026 0001001 M026 0001001 M026 0001001 M026 000

1001 M026 0001001 M026 0001001 M026 000

1001 M026 0001001 M026 0001001 M026 000

DD6


DD9

4

DE9

20

DF9

10

DG9

10

DD10


DE10


DF10

DEFINITION Specifies the name of the planning version .

DG10

DEFINITION USE The SNP demand profile enables you to define how demand is calculated in SNP heuritic and deployment planning runs for Supply Network Planning (SNP). In this way, you can define the forecast horizon in which the system does not consider the forecast as part of the total demand, as well as the pull deployment horizon in which the deployment considers the planned distribution demand. If you want to make the same demand calculation settings for several products, you can define them in one SNP demand profile. These setting are then considered in the location product master, but cannot be changed there. DEPENDENCIES EXAMPLE

DE11


1001 M028 0001001 M028 0001001 M028 0001001 M028 000

1001 M028 0001001 M028 000

1001 M028 0001001 M028 0001001 M028 0001001 M028 0001001 M028 0001001 M028 000

1001 M027 0001001 M027 0001001 M027 0001001 M027 0001001 M027 000

1001 M027 0001001 M027 0001001 M027 000

1001 M027 0001001 M027 0001001 M027 0001001 M027 0001001 M027 0001001 M027 000

1002 L044 0001002 L044 0001002 L044 0001002 L044 000

forecast_horizon pull_deplmt_horizon

Supply Network Planning: Forecast Horizon in Days SNP: Pull Deployment Horizon (in Days)/sapapo/snpfcsth /sapapo/snppullh

dec/ 3/ 0 dec/ 3/ 0

DH9

3

DI9

3

DH10

DEFINITION Horizon in calendar days during which the forecast is not considered as part of the total demand. Use Within this horizon, Supply Network Planning (SNP) does not take the forecast into account when calculating total demand. Outside of this horizon, the system calculates total demand using either the forecast or sales orders (whichever value is larger), and the other demands (dependent demand, distribution demand, planned demand, and confirmed demand). Dependencies If you have defined a requirement strategy on the Demand tab page of the location product master, the system calculates the total demand outside of the forecast horizon either as a total of the forecast and sales orders (strategy 20, Planning with Final Assembly) or only uses the forecast (strategy 10, Make-to-Stock Production). The SNP and deployment optimizers only take into account the forecast horizon if you have set the Forecast Horizon indicator on the Integration tab page of the SNP optimizer profile or SNP deployment optimizer profile. Example The situation at the start of the month is as follows: Demand of 10 pieces is forecast for the 10th, 20th, and 30th of the month. There are sales orders of 5, 5, and 15 pieces respectively on the 10th, 20th, and 30th of the month. No requirements strategy has been specified in the location product master. The defined forecast horizon is 15 days. Result: After the planning run, the following is displayed in the Total Demand key figure in interactive Supply Network Planning: 5 pieces on the 10th, 10 pieces on the 20th, and 15 pieces on the 30th of the month.

DI10

DEFINITION Period of time over which deployment considers the planned distribution demand. The horizon starts from today's date. Use Deployment Heuristic During the deployment run, the system attempts to fulfill the total distribution demand within this defined horizon. Distribution starts on the first day on which distribution demands exist in the system and ends with the last day of the pull deployment horizon. The pull deployment horizon is also used during push distribution (which you define in the deployment profile or location product master). The pull deployment horizon determines whether demand is to be fulfilled immediately (push rule P or Pull/Push) or according to the due date (push rule blank or Pull). The due date restricts the date by which SNP stock transfers are considered as relevant for deployment. Within this horizon, deployment only fulfills planned demand that is confirmed. Push rule X (push distribution by demands) ignores the pull deployment horizon. Dependencies You can define the pull deployment horizon for the deployment optimizer in both the location product master and the SNP deployment optimizer profile (on the Deployment Parameter) tab page. If you want the deployment optimizer to take into account the value defined in the location product master, you have to enter a value of > 0 in the location product master and set the Use Horizons from Product Master indicator in the deployment optimizer profile. If you do not do this, the system uses the value you defined in the deployment optimizer profile. Example Situation at the start of the month: The pull deployment horizon is 15 days long. Distribution demand is planned for the 10th and 20th of the month. Result: Deployment only considers distribution demand that has been confirmed for the demand planned on the 10th of the month.

period_split vmi_prom_lead_time

Indicator for Time-Based Demand Distribution (Period Split) VMI Promotion Lead Time/sapapo/snppspli /sapapo/prmty

char/ 1/ dec/ 11/ 0

DJ6

Split According to Workdays (Entire Period) 1 Split According to Workdays (Proportional Period) 2 Split Entire Quantity Over Remaining Workdays

DK8


DJ9

1

DK9

10

DJ10

DEFINITION Defines how planning data is disaggregated by time when you release the demand plan from Demand Planning to Supply Network Planning. WHAT_TO_DO To define the period split, you choose one of the following options: Blank The data is disaggregated and released to all of the workdays in the specified horizon. '1' The data is disaggregated to all of the workdays in the specified horizon, but released only for those days that lie in the present and future. '2' The data is disaggregated to the workdays in the present and future, and then released for the same days. EXAMPLES The date is November 1st, 2000. The release horizon is the week from October 30th through November 3rd. The demand plan for this week is 150 boxes. Depending on which option you choose, the data is disaggregated and released as follows: You leave this field blank. ,,Oct 30 ,,Oct 31 ,,Nov 1 ,,Nov 2 ,,Nov 3 ,,30 ,,30 ,,30 ,,30 ,,30 You enter a '1'. ,,Oct 30 ,,Oct 31 ,,Nov 1 ,,Nov 2 ,,Nov 3 ,, - ,, - ,,30 ,,30 ,,30 You enter a '2. ,,Oct 30 ,,Oct 31 ,,Nov 1 ,,Nov 2 ,,Nov 3 ,, - ,, - ,,50 ,,50 ,,50 DEPENDENCIES The prerequisite for using this field is that you have specified which storage buckets profile is to be used for the release to SNP. This storage buckets profile must contain days only. You specify the storage buckets profile: In the transfer profile, if you are carrying out mass processing By choosing Demand Planning -> Environment -> Release to SNP, if you are releasing the demand plan online

DK10

Like the target days supply, which refers to total demand without VMI promotions, and is specified in the lot size profile, this lead time refers to the number of days required to satisfy demand, specifically for VMI customer promotions (see key figure VMI promotions) prior to their due date. The VMI promotional lead time is only used at customer locations that are part of a VMI scenario. All other demand key figures, such as sales orders, are processed according to the target days supply. The VMI promotions key figure is processed according to the VMI promotional lead time. Specify the number of workdays allocated as lead time to cover a VMI customer's product promotion. In a VMI scenario, you set up a VMI InfoCube in Demand Planning which contains demand data to be released to the supply network planning key figure, VMI promotion, at a VMI customer location. The VMI promotional lead time indicates the lead time needed for the Supply Network Planner to schedule the specific VMI forecast demand. If you do not maintain the VMI promotional lead time in this profile, this information and the information labeled VMI promotions target stock does not appear in the planning table. The VMI promotions key figure appears in interactive planning only when you select a customer location. Situation: You have a VMI demand on the 20th of the month in your supply network planning key figure, VMI promotions, and a VMI promotional lead time of 10 days. Result: The distribution receipts for the VMI demand will be scheduled on the 10th of the month.

past_fc_horizon_flag supply_profile

Take Into Account Forecast Horizon in Past Supply Network Planning: External Supply Profile/sapapo/snpfcconsum /sapapo/snpsprex

char/ 1/ char/ 10/

DL6

X TRUE FALSE

DL9

1

DM9

10

DL10

DEFINITION USE This indicator refers to the Forecast Horizon . If you do not specify a value for the forecast horizon or enter the value 0, and set this indicator, the consumption logic of the forecast horizon also applies for planning periods situated in the past (before today's date). DEPENDENCIES EXAMPLE

DM10

DEFINITION USE The SNP supply profile enables you to specify how supply (that is, key figures such as production and distribution receipt) is calculated in SNP heuristic and deployment heuristic planning runs for Supply Network Planning (SNP). In this way, you can define the production horizon in which SNP does not plan production, as well as the stock transfer horizon in which SNP does not plan stock transfers, for instance. You can also define the push deployment horizon in which the deployment heuristic considers receipts defined in the ATD receipt category group in the location master data. If you want to make the same supply calculation settings for several products, you can define them in one SNP supply profile. These settings are then considered in the location product master, but cannot be changed there. DEPENDENCIES EXAMPLE

production_horizon prod_horizon_period production_horizon_extn

SNP Production Horizon Period Category Extended SNP Production Horizon (in Days)/sapapo/snpprodh /sapapo/period_type /sapapo/snpphext

dec/ 3/ 0 char/ 2/ dec/ 3/ 0

15151515

15151515

15151515

151515

DO6

Day W Week (From Monday) W0 Week (From Sunday) M Month

DN9

3

DO9

2

DP9

3

DN10

DEFINITION Horizon in which Supply Network Planning (SNP) and Capable-to-Match (CTM) do not plan production. Use You divide the areas of responsibility for planning between the SNP production horizon and the PP/DS Horizon: You plan production with SNP or CTM outside of the SNP production horizon; planning is bucket-oriented and usually stretches over the medium-term horizon. In the short-term horizon, that is the PP/DS horizon, you plan production in more detail using automatic Production Planning and Detailed Scheduling (PP/DS). You can manually create PP/DS orders outside of the PP/DS horizon. Therefore, the SNP production horizon is only relevant for SNP and CTM and does not cause constraints on order generation at PP/DS level. If the SNP production horizon is shorter than the PP/DS horizon, the planning areas overlap. This means that planning tasks require full reconciliation. Use in SNP SNP does not create any planned orders in the Production (planned) key figure, but moves production to the first day after this horizon. SNP deletes all unfixed SNP planned orders from previous planning runs within this horizon. The horizon starts on the system date (or date defined in the Planning Start Date field of the planning book or using the PDATE user exit for background processing). Use in CTM CTM does not generate or delete any planned orders within this production horizon. The horizon starts on the system date (or the date you specified as the planning start in the CTM profile). If no value has been specified here, CTM takes into account the PP/DS Horizon in the planning version. Use in PP/DS If you do not enter any value for the PP/DS horizon or if you enter the duration '0', the system automatically uses the SNP production horizon as the PP/DS horizon. Therefore, the PP/DS horizon is as long as the SNP production horizon. This means the planning intervals for SNP and PP/DS are sequenced with no gaps or overlaps. For more information, see Adjusting the PP/DS Horizon. Note If you want to plan the receipts created in SNP or CTM in detail, convert the SNP or CTM orders into PP/DS orders. Dependencies In the Fix Production field, you can specify that SNP is to consider all SNP planned orders from previous planning runs as fixed in this horizon and therefore does not delete them. You use the Period Category field to specify that the SNP production horizon is defined in calendar days, weeks, or months. This setting can influence data consistency, particularly regarding integration of SNP planned orders with SAP R/3. Example Situation at the start of the month: The production horizon is 15 days long. Distribution demands arise at a plant on the 10th und 20th of the month. The target days' supply at the plant is zero. Result: Production for the distribution demands is planned for the 15th and the 20th of the month. The demands within the SNP production horizon are planned including due date overruns in Supply Network Planning.

DO10

DEFINITION Determines whether the specified SNP production horizon or SNP stock transfer horizon is defined in calendar days, weeks (calculated from a Monday or Sunday), or months. USE At the end of the current period of the period category that has been set, the SNP production horizon or SNP stock transfer horizon moves one period into the former SNP planning horizon. We recommend that you choose a period category for the SNP production horizon or SNP stock transfer horizon that corresponds to the set frequency of your SNP planning. This avoids data inconsistencies (if SNP planned order integration is configured) caused by planned orders transferred from SAP R/3. DEPENDENCIES EXAMPLE You are performing SNP planning on a weekly basis, starting every Sunday. You choose period categroy WO (weekly from a Sunday) for the SNP production horizon. The SNP production horizon ends on the Saturday of the current week. On the Sunday, it moves one week into the former SNP planning horizon.

DP10

DEFINITION Time period over which Supply Network Planning (SNP) and Capable-to-Match (CTM) do not plan production; that is, do not create any planned orders. SNP and CTM move production to the first day after this horizon. This horizon is an extension of the SNP Production Horizon. However, in contrast to the SNP production horizon, you can manually create SNP planned orders in this extended horizon in interactive Supply Network Planning. USE DEPENDENCIES EXAMPLE

15151515

1515

1515151515

151515

stock_transfer_horizon tf_horizon_period push_horizon

SNP Stock Transfer Horizon Period Category SNP: Push Deployment Horizon (in Days)/sapapo/snpshiph /sapapo/period_type /sapapo/snppushh

dec/ 3/ 0 char/ 2/ dec/ 3/ 0

DR6

Day W Week (From Monday) W0 Week (From Sunday) M Month

DQ9

3

DR9

2

DS9

3

DQ10

DEFINITION Horizon during which neither Supply Network Planning (SNP) nor Capable-to-Match (CTM) plan stock transfers. USE In contrast to the SNP Production Horizon, this horizon prevents stock transfers from being planned too last minute , leaving insufficient time for the organization to react. Use in SNP Enter the number of days, weeks, or months during which the system is not to plan stock transfers. The time period starts on the system date (or if required, the date specified in the Planning Start Date field of the planning book or in the PDATE user exit for background processing). The system does not generate any planned distribution receipts within this horizon; instead, it moves them to the first day after the SNP stock transfer horizon. SNP also deletes all non-fixed stock transfers from previous planning runs within this horizon. Use in CTM CTM does not generate or delete any stock transport requisitions within this stock transfer horizon. The horizon starts from the system date (or if required, on the date you specified in the Planning Start field of the CTM profile). Dependencies You can specify in the Fix Stock Transfers field that you want SNP to consider all stock transfers from previous planning runs as fixed in this horizon and therefore not delete them. In the Period Category field, you can set whether SNP stock transfer horizon is to be defined in calendar days, weeks, or months. This setting can influence data consistency in the integration of SNP planned orders with SAP R/3.

DR10

DEFINITION Determines whether the specified SNP production horizon or SNP stock transfer horizon is defined in calendar days, weeks (calculated from a Monday or Sunday), or months. USE At the end of the current period of the period category that has been set, the SNP production horizon or SNP stock transfer horizon moves one period into the former SNP planning horizon. We recommend that you choose a period category for the SNP production horizon or SNP stock transfer horizon that corresponds to the set frequency of your SNP planning. This avoids data inconsistencies (if SNP planned order integration is configured) caused by planned orders transferred from SAP R/3. DEPENDENCIES EXAMPLE You are performing SNP planning on a weekly basis, starting every Sunday. You choose period categroy WO (weekly from a Sunday) for the SNP production horizon. The SNP production horizon ends on the Saturday of the current week. On the Sunday, it moves one week into the former SNP planning horizon.

DS10

DEFINITION Period of time over which deployment considers receipts that were defined in the ATD Receipt category group of location master data. The horizon starts from today's date. Use Deployment Heuristic If push distribution has been defined in the deployment profile or location product master (if distribution demand is less than supply and stock on hand), the push deployment horizon determines whether stock on hand is to be distributed before the due date of the distribution demand according to the defined push rule. Only stock on hand within the push deployment horizon is taken into account for push deployment (that is, deployment before the actual demand date). DEPENDENCIES You can define the push deployment horizon for the deployment optimizer in the location product master and in the SNP deployment optimizer profile (on the Deployment Parameters tab page). If you want the deployment optimizer to take into account the value defined in the location product master, you have to enter a value that is > 0 and set the Use Horizons from Product Master indicator in the deployment optimizer profile. If you do not do this, the system uses the value that you defined in the deployment optimizer profile. Example Situation: Start of the month The push deployment horizon is 15 days long Production is confirmed for day 10 Production is confirmed for day 20 The ATD receipt category group contains unrestricted-use stock and categories for confirmed production Result: During deployment calculations, the system takes into account the production confirmed for day 10.

21212121

safty_stock_push_horizon fix_planning_orders_flag

Deployment: Safety Stock Push Horizon SNP: Fix Planning Orders/sapapo/depsbpuh /sapapo/snpprodf

dec/ 3/ 0 char/ 1/

DU6

X TRUE FALSE

DT9

3

DU9

1

DT10

DEFINITION USE This horizon is considered by deployment in Supply Network Planning (SNP) if you choose push distribution rule S (Push taking the safety stock horizon into account) on the SNP 2 tab page of the location product master. The system only confirms planned issues that would have to be covered by safety stock at the source location if the difference between the demand and deploy date is smaller than the safety stock horizon. This means that the system only allows the safety stock level that you defined on the Lot Size tab page of the location product master to be fallen below if the demand to be fulfilled is in the safety stock horizon. DEPENDENCIES EXAMPLE There is a 5-day safety stock horizon and a safety stock of 100 pieces. On deploy date 1, the available-to-deploy quantity (ATD quantity) at the source location is 200 pieces. On day 7, there is a planned distribution demand of 200 pieces. When you run deployment, the system will confirm a quantity of 100 pieces for day 1. The safety stock of 100 pieces remains at the source location. Only on day 3, when the interval between the deploy date and demand date is less than or equal to 5 days, will the remaining quantity of 100 pieces be confirmed.

DU10

DEFINITION USE SNP Heuristic If you set this indicator, all SNP planned orders from previous planning runs that are within the SNP Production Horizon, are considered as fixed during the heuristic run in Supply Network Planning (SNP) and, therefore, are not deleted. SNP Optimizer If you set this indicator, all SNP planned orders from previous planning runs that are outside of the planning horizon specified for background processing, are considered as fixed during the SNP optimization run and, therefore, are not deleted. If you do not set this indicator, all SNP planned orders from previous planning runs that fall within the planning buckets profile specified for the planning book are deleted during the SNP optimization run. In this instance, the SNP production horizon is an exception: If you have specified in the SNP optimizer profile that you want the optimizer to take the SNP production horizon into account, no SNP planned orders are deleted in this horizon. DEPENDENCIES EXAMPLE

fix_stock_transfers_flag deployment_profile

Supply Network Planning: Fix Stock Transfers Supply Network Planning: External Deployment Profile/sapapo/snpshipf /sapapo/snpdplex

char/ 1/ char/ 10/

DV6

X TRUE FALSE

DV9

1

DW9

10

DV10

DEFINITION USE SNP Heuristic If you set this indicator, all SNP stock transfers from previous planning runs that are within the SNP stock transfer horizon are considered as fixed during the heuristic run in Supply Network Planning (SNP) and, therefore, are not deleted. SNP Optimizer If you set this indicator, all SNP stock transfers from previous planning runs that are outside of the planning horizon specified for background processing, are considered as fixed during the SNP optimization run and, therefore, are not deleted. If you do not set this indicator, all SNP stock transfers from previous planning runs that fall within the planning buckets profile specified for the planning book are deleted during the SNP optimization run. In this instance, the SNP stock transfer horizon is an exception: If you have specified in the SNP optimizer profile that you want the optimizer to take the SNP stock transfer horizon into account, no SNP stock transfers are deleted in this horizon. DEPENDENCIES EXAMPLE

DW10

DEFINITION The SNP deployment profile enables you to define distribution rules for the deployment heuristic in Supply Network Planning (SNP) that the system uses to distribute the available product quantities to demand locations. If supply exceeds demand, you can define the fair share rules, and if demand exceeds supply, the push rules can be defined. If you want to make the same distribution rule settings for several products, you can define them in one SNP deployment profile. These setting will then be considered in the location product master, but they cannot be changed there. USE DEPENDENCIES EXAMPLE

faire_share_rule push_distribution priority demand_selection_period

Fair Share Rule Indicator: Push Distribution Product Priority Demand Selection Horizon (in Days)/sapapo/snpdplfs /sapapo/snpdplpu /sapapo/prio /sapapo/ctmdselhorz

char/ 2/ char/ 1/ int1/ 3/ dec/ 3/ 0

DX6

A Proportional Distribution Based on Demands B Proportional Fulfillment of Target C Proportional Distribution Based On Quota Arrangement D Proportional Distribution Based On Priorities X User-Defined Fair-Share Distribution

DY6

Pull P Pull/Push X Push by demands Q Push by quota arrangement S Push taking the safety stock horizon into account U User-defined distribution

DX9

2

DY9

1

DZ9

3

EA9

3

DX10

DEFINITION If demand exceeds supply, the system may use fair share logic to calculate deployment based on the available-to-deploy quantity (ATD quantity) These fair share rules allow for alternative methods of allocating a restricted supply of product to the demand sources. Use You specify a fair share rule to determine how you want the fair share logic to be applied: The objective of fair share rule A is to distribute the stock proportionally to all demand locations according to planned distribution demand. The objective of fair share rule B is to raise the stock levels in all demand locations to approximately the same percentage of target stock level. The percentage per destination location is defined as deployment-relevant stock (= stock on hand - SNP stock transfers) divided by the target stock level. If there is a negative projected stock level, the system first attempts to raise the stock level at all destination locations to zero. The system then attempts to raise the stock level at all destination locations to the same percentage of target stock level. The objective of fair share rule C is to distribute the stock according to quota arrangements at the demand locations. The objective of fair share rule D is to distribute stock according to distribution priorites maintained at the transportation lanes. Destination location requirements are confirmed in order of priority as long as there is an existing ATD quantity. Destinations with lower priority receive only partial or no stock allocation. Dependencies In order to apply fair share rule C, you have to define outbound quota arrangements for source location products in master data or the Supply Chain Engineer. In order to apply fair share rule D, you have to maintain distribution priorities at the transportation lanes. Note that the default value is set as 0 (the highest possible priority).

DY10

DEFINITION Push rules are used to calculate deployment in Supply Network Planning (SNP) if the available-to-deploy (ATD) quantity covers the demand. Use By specifying a push rule, you determine how you want the push logic to be used: With Pull distribution, deployment covers all the demand within the pull deployment horizon. Products are distributed on the due dates specified at each demand location. Nothing is distributed to the demand location in advance of the demand date. With Pull/push distribution, the entire supply is distributed immediately to the demand locations to cover all demand within the pull deployment horizon. The demand dates specified at the demand locations are ignored in this instance. With Push by demands, the entire supply is distributed immediately to the demand locations for the entire planning horizon to cover all demands. The pull deployment horizon is ignored in this instance . With Push by quota arrangement, the entire supply is distributed immediately according to the set quota arrangements for the demand locations. The demand situation at the destination locations is ignored in this instance. With Push taking the safety stock horizon into account, the system only confirms planned issues that are to be covered by safety stock at the source location if the difference between the demand and deploy date is smaller than the safety stock horizon. This means, the system will only fall below the safety stock level that you defined on the Lot Size tab page of the location product master if the demand to be fulfilled is in the safety stock horizon. Note that the safety stock horizon moves forward with planning. Dependencies The push deployment horizon is the period over which the supply available at the source location can be deployed (ATD quantity). The pull deployment horizon is the period over which the planned distribution demand at the source location can be deployed. You define the above two horizons and the safety stock horizon on the SNP 2 tab page of the location product master. If you set the Push not allowed indicator on the SNP tab page of the location master (only possible in active version), the available supply is distributed according to the daily demand at the demand location only.

DZ10

Use The system can derive the priority of the order from the priority of the product. You can assign values from 0 to 255 for the priority. The value 1 represents the highest priority, whereas 255 is the lowest priority you can enter. If you enter the value 0 or no value, the system equates this with priority 256. You can maintain the priority on the SNP2 tab page only. The priority field on the PP/DS tab page is display only. Use in PP/DS In production planning and detailed scheduling(PP/DS), the order priority can be derived from the product priority or the sales order. On the basis of the order priority, you can make a planning decision, for example, or carry out a sequence planning using a detailed scheduling heuristic. You specify which priority the system uses in PP/DS in the planning version (PP/DS: Determination of Order Priorities field). Use in CTM Capable-to-Match Planning (CTM) takes into account the value for the prioritization in requirement prioritization. For this purpose, you must specify on the Requirements tab page in the Capable-to-Match profile that the requirements are to be prioritized according to the criterion MATPRIO. However, the value specified here is not taken into account if you have entered a value for priority and/or rank in the location product master record under time-dependent priority. Use in SNP In Supply Network Planning(SNP), the product priority is only used in the area of capacity leveling. This field is not taken into account in the SNP heuristic, the SNP optimizer, deployment, or the Transport Load Builder (TLB). For capacity leveling, you can specify in the Order Prioritization (or Priority ) field that the product priority is to be taken into account. The system then moves orders for products with the highest priority first to earlier periods or orders for products with the lowest priority first to later periods, depending on the system setting.

EA10

DEFINITION USE You can limit the selection period for demands that Capable-to-Match Planning (CTM) uses, depending on product. If, for example, you plan products with different lead times, you can determine the selection horizon for the demands of one product in a different way to the selection horizon for the demands of another product. The value that you enter here in days determines the end date of the selection horizon, starting on the current date. If the value entered here is after the original end date, the system keeps this original end date. The value entered here does not affect the starting date of the selection horizon determined in the CTM profile or order selection. DEPENDENCIES If you have set the Ignore Prod-Spec. Sel. Horizon Demands indicator, CTM planning only considers the entries in the order selection or in the CTM profile. If you have set the Relate Horizons to Planning Start indicator in the CTM profile, the product-dependent selection period does not relate to the current date, but to the planning start date. EXAMPLE

order_creation_period

Order Creation Frame (Horizon for Creating Orders)/sapapo/ctmearlyship

numc/ 3/

EB9

3

EB10

DEFINITION Period before demand date (in days), in which Capable-to-Match Planning (CTM) can create planned orders to fulfill a demand. USE You can enter values between 1 - 999 . The start date of all orders created by CTM planning must lie within the specified time period (demand date minus number of calendar days). Remember that the system counts non-workdays as days. The period is valid for all orders created for one demand, independent of the BOM level. Existing receipts or stocks, however, do not have to lie in this period. This includes receipts that CTM planning creates because of the manufacture of co-products or lot size specifications, and does not consume immediately. DEPENDENCIES The period specified here to create orders does not influence the settings that you made for late demand fulfillment. EXAMPLE

requirement_profile requirements_strategy

Ext. No. of PP Demand Profile in Material Master Record Requirements Strategy/sapapo/rqmky /sapapo/stra1

char/ 10/ char/ 2/

ED8

Valuetable: /SAPAPO/STRATEGY

EC9

10

ED9

2

EC10

DEFINITION Demand profiles store frequently used settings for the Demand tab page of location products. Rather than entering the same settings for several location products, you simply assign a demand profile to the location product on the Demand tab page. The settings are then automatically included. If you change the demand profile, the settings are changed in all the location products to which the profile has been assigned. Once you have assigned a demand profile to a location product, you cannot changes the settings manually. The Alert filter is not included in the demand profile.

ED10

DEFINITION Determines how quantities forecasted in APO Demand Planning are produced , and how the demand forecast is consumed with sales orders. SAP delivers the requirements strategies listed below. You can also define your own strategies, see Define Requirements Strategy. 10 Make-to-stock production Choose this strategy if sales orders do not influence production; for example, in a mass production environment where individual orders do not affect the amount produced. There is no consumption of the forecast by incoming sales orders. 20 Planning with final assembly Choose this strategy if you can accurately forecast production quantities for the final product. With this make-to-stock strategy, production quantities take into account actual sales orders as well as forecasted demand: incoming sales orders consume the forecast, and production quantities result from the net demand. The advantage of this strategy is that you can react quickly to customer demand. 30 Planning w/o final assembly Choose this strategy if the main value-added process is final assembly; that is, the amount of the sales order is fixed and production is unique for every customer. With this make-to-order strategy, only the product's component parts are produced prior to the taking of the sales order. The sales order consumes the forecast for the finished product and triggers production of the finished product. 40 Planning product Choose this strategy to plan non-variable parts for similar finished products and reserve the capacities that are required to produce them. This strategy ensures a rapid response to customer demand and is particularly useful for products that have a long manufacturing lead time. The value-adding process is not carried out until the customer has placed their order. The planning product can be either a fictive entity that is never produced, or it can be a product that is actually produced. For more information, see the release note Requirements Strategy 40.

40404040

dep_requirements_option period_profile consumption_mode

Dependent Requirements Ind. for Individual and Coll. Reqmts Period Profile ID Consumption Mode/sapapo/sbdkz rpm_tbid /sapapo/vrmod


EE6

Individual requirements if possible 1 Individual requirements if possible 2 Collective requirements only

EG6

1 Backward Consumption Only 2 Backward/Forward Consumption 3 Forward Consumption Only

EE9

1

EF9

22

EG9

1

EF10

DEFINITION Key that uniquely identifies a specific period profile. USE You use a period profile to define the periods (buckets) in which the component requirements determined by the planning matrix are to be aggregated. The system aggregates the dependent requirements for components that you have indicated for aggregation (the always collective requirements indicator is set) in the material or product master. DEPENDENCIES You can only use the period profile if you use the planning matrix (RPM) to plan components. You create the period profile in Customizing for the Planning Matrix (RPM) and assign it in the product master to the components that you want to aggregate. EXAMPLE

EG10

DEFINITION Controls the direction on the time axis in which the system consumes the forecast. Backward consumption Sales orders consume forecasted quantities that lie before the requirements date. Backward/forward consumption Sales orders consume forecasted quantities that lie before the requirements date. If the actual demand is not satisfied, the sale orders then consume forecasted quantities that lie after the requirements date in order to satisfy the remaining demand. Forward consumption Sales orders consume forecasted quantities that lie after the requirements date.

backw_consump_period forw_consump_period consumption_group

Backward Consumption Period Forward Consumption Period Consumption Group/sapapo/vint1 /sapapo/vint2 /sapapo/bdgrp

numc/ 3/ numc/ 3/ char/ 10/

EH9

3

EI9

3

EJ9

10

EH10

DEFINITION Defines the consumption period (in calendar days) for backward consumption. In backward consumption, sales orders, dependent requirements or material reservations consume forecasted demand that lies within the consumption period and before the requirements date. The backward consumption period becomes valid on the date on which you enter it. WHAT_TO_DO Enter a backward consumption period of between 1 and 999 days. DEPENDENCIES If you have chosen consumption mode 1 or 2, enter a backward consumption period. HINWEIS The consumption period is in calendar days not workdays. Since SNP and PP/DS can use different calendars, it is not possible to define a calendar for use with consumption. This may lead to unexpected results.

EI10

DEFINITION Defines the consumption period (in calendar days) for forward consumption. In forward consumption, sales orders, dependent requirements or material reservations consume forecasted demand that lies within the consumption period after the requirements date. The forward consumption period becomes valid on the date on which you enter it. WHAT_TO_DO Enter a forward consumption period of between 1 and 999 days. DEPENDENCIES If you have chosen consumption mode 2 or 3, enter a forward consumption period. HINWEIS The consumption period is in calendar days not workdays. Since SNP and PP/DS can use different calendars, it is not possible to define a calendar for use with consumption. This may lead to unexpected results.

EJ10

DEFINITION If you want to work with descriptive characteristics in applications other then Demand Planning, you specify these characteristics in a consumption group. In the consumption group you assign fields from the ATP field catalog to characteristics in Demand Planning. Consumption groups are used in conjunction with descriptive characteristics to enable the forecast to be consumed by sales orders and related orders, at a more detailed level than the location product. For instance you may want to create forecasts for individual customers and to then consume this forecast when the customer places a sales order. You use consumption groups to do this This gives you significantly more flexibility when planning orders. For instance you can assign priorities to customers , so that your most important customer gets preference if all orders cannot be satisfied in a particular period. The accepted orders can then be subtracted from the forecast at customer level. You create consumption groups in Customizing for Demand Planning under Basic Settings ->Maintain Consumption Group

7 07 07 07 0

subassembly_planning_flag pegging_strategy avoid_alerts_flag

Assembly Planning Pegging strategy for dynamic pegging Avoid Alerts in Pegging/sapapo/rrp_miskz /sapapo/peg_strategy /sapapo/peg_wo_alert_first


EK6

X Yes No

EL6

00 Use Timely Receipts 01 Use Earliest Receipts (first in first out)

EM6

Ignore Alerts X Time and Quantity Alerts

EK9

1

EL9

2

EM9

1

EK10

use This indicator is relevant, if the product is an assembly. Dependent requirements, stock transport requirements or order reservations can appear for an assembly. For example, dependent requirements arise for the assembly during planning of a finished product that the assembly contains as a component. Set the indicator If you want the system to offset these requirements with the planned independent requirements for the assembly If you want to check the availability of the product against the forecast during the multilevel ATP check recommendation Forecast consumption is time-consuming. For performance reasons, you should only set this indicator if it is really necessary for the planning. dependencies In order that the system carries out consumption, you must have specified a relevant requirements strategy.

EL10

use Using the pegging strategy, you can determine in which time sequence the system should cover requirements for the product with dynamic pegging and in which time sequence the system should use the product receipts in the pegging interval to cover a requirement. Thus, the pegging strategy controls, Which requirement the system should cover first Which receipts the system should use first Generally, for dynamic pegging, the system begins by covering the earliest requirement, and then processes the next requirement, and so on. Since there may be several receipts for the availability dates/times within the pegging interval, you must specify which receipt the system should use first. The following options exist: Use current receipts Here the system uses the current receipt where possible to cover a requirement. Starting from the requirement date the system first searches to the beginning of the pegging interval. If there are no receipts in this direction, the system will search to the end of the pegging interval. Use the earliest receipt (First in first out) Here the system uses the earliest receipts in the pegging interval to cover a requirement, that is, first the first receipt in the pegging interval and then the second, and so on. With this strategy, excess receipts only become available later. Note In principle, only receipts and requirements from the same pegging area can be linked.

EM10

use If you set this indicator, the system attempts to create the pegging relationships between requirements and receipts if possible without quantity alerts or date alerts. First, the system links receipts and requirements that are compatible on a time and quantity basis, then the remaining receipts and requirements in a second step. Note This method can reduce performance.

receipt_max_earliness receipt_max_lateness

Maximum Allowed Earliness for a Receipt Element Maximum Allowed Lateness for a Receipt Element/sapapo/dm_pegging_future /sapapo/dm_pegging_past_max

dec/ 11/ 0 dec/ 11/ 0

EN8


EO8


EN9

10

EO9

10

EN10

use For dynamic pegging, the system can only use a receipt to cover a requirement if the availability date/time is not earlier than the specified timeframe before the requirements date/time. The system cannot assign even earlier receipts to the requirement. You can therefore exclude receipts that are too early for a requirement and thus avoid storage problems, for example. You specify the timeframe in the format HHH.HHH:MM (hours:minutes). Example: 1.000:10 means 1000 hours and 10 minutes, 20:20 means 20 hours and 20 minutes. If you do not specify a value, the system uses the value 100000:00. Therefore, the system may only assign a receipt to a requirement if the availability date/time is at most 100000 hours before the requirements date/time. dependencies Pegging Interval The maximum allowed earliness and the maximum allowed delay for a receipt together define the pegging interval for a requirement. For dynamic pegging, the system can only cover requirements with receipts whose availability date/time lies within the pegging interval. Pegging Interval when Creating New Orders If the quantities of the receipts in the pegging interval are not sufficient to cover a requirement, there is a shortage. The system can create orders using automatic planning and then assign them to the requirement (as long as the receipt deadlines lie within the pegging interval). You can determine if the system should create orders so that the availability dates/times are within the pegging interval using the Detailed Scheduling strategy . If the availabilty dates/times for the new orders are outside the pegging interval, the system cannot create a dynamic pegging relationship. This means that the shortage will still exist for the requirement and the new receipts will create a surplus (if the system does not use these receipts to cover other requirements). Alerts The system can create alerts for quantity problems (shortage or surplus) and for deadline problems. A deadline problem occurs if the availability date/time for a dynamic pegging relationship is before or after the requirements deadline, the product therefore being available either too early or too late. In the Date/Time Alerts segment you can determine from which variances the system should create alerts for receipts which are too early or too late. The threshold values for the date/time alerts should be within the pegging interval. To allow the system to display quantity and date/time alerts, you must use an appropriate PP/DS alert profile in the interactive planning.

EO10

use For dynamic pegging the system can only use a receipt to cover a requirement if the availability date/time is not later than the specified timeframe after the requirements date. The system cannot assign even later receipts to the requirement. You can therefore exclude receipts which are too late for a requirement and thus avoid problems with missing materials or with the customer. You specify the timeframe in the format HHH.HHH:MM (hours:minutes). Example: 1.000:10 means 1000 hours and 10 minutes, 20:20 means 20 hours and 20 minutes. If you do not specify a value, the system uses the value 0. Therefore, the system may not assign any late receipts to a requirement. dependencies Pegging interval The maximum allowed earliness and the maximum allowed delay for a receipt together define the pegging interval for a requirement. For dynamic pegging, the system can only cover requirements with receipts whose availability date/time lies within the pegging interval. Pegging Interval when Creating New Orders If the quantities of the receipts in the pegging interval are not sufficient to cover a requirement, there is a shortage. The system can create orders using automatic planning and then assign them to the requirement (as long as the receipt deadlines lie within the pegging interval). You can determine if the system should create orders so that the availability dates/times are within the pegging interval using the Detailed Scheduling strategy . If the availabilty dates/times for the new orders are outside the pegging interval, the system cannot create a dynamic pegging relationship. This means that the shortage will still exist for the requirement and the new receipts will create a surplus (if the system does not use these receipts to cover other requirements). Alerts The system can create alerts for quantity problems (shortage or surplus) and for deadline problems. A deadline problem occurs if the availability date/time for a dynamic pegging relationship is before or after the requirements deadline, the product therefore being available either too early or too late. In the Date/Time Alerts segment you can determine from which variances the system should create alerts for receipts which are too early or too late. The threshold values for the date/time alerts should be within the pegging interval. To allow the system to display quantity and date/time alerts, you must use an appropriate PP/DS alert profile in the interactive planning.

no_dynamic_pegging_flag concurrent_pegging_flag split_time_interval

Deactivate Dynamic Pegging Concurrent Pegging Duration of Time Interval for Concurrent Pegging/sapapo/peg_no_dyn /sapapo/peg_concurrent /sapapo/peg_lot_time

char/ 1/ char/ 1/ dec/ 11/ 0

EP6

Use dynamic pegging X Do not use dynamic pegging

EQ6

No X Yes

ER8


EP9

1

EQ9

1

ER9

10

EP10

DEFINITION USE If you do not set this indicator, dynamic pegging is active for the location product. That is to say, the system can create dynamic pegging relationships between requirement elements and stock or receipt elements. If you set this indicator, the system does not carry out dynamic pegging for the location product - that is to say, there are no dynamic pegging relationships. DEPENDENCIES Note that deactivation of dynamic pegging has consequences for all applications that use dynamic pegging and evaluate dynamic pegging relationships. In addition to detailed scheduling, PP/DS optimization, and certain PP/DS heuristics, the display of alerts is affected. Without dynamic pegging, the system does not generate quantity alerts for requirement and receipt elements. In other words, all receipts represent surpluses and all requirements are regarded as insufficiently covered. Furthermore, the system cannot generate date/time alerts. Only if you reactivate dynamic pegging can the applications involved carry out dynamic pegging again and evaluate the dynamic pegging relationships accordingly. EXAMPLE NOTE

EQ10

use This indicator is relevant to dynamic pegging for orders with continuous requirements or receipts. Continuous requirements or receipts of various orders can overlap. If you set the indicator, the system uses concurrent pegging. In concurrent pegging the system splits the quantities, which consume or make available two overlapping continuous requirements or receipts in the overlapping phase, into partial quantities. A partial quantity is the quantity that a requirement or a receipt requires or makes available in a time interval with a user-specific duration. The system distributes these partial quantities; that is, it creates dynamic pegging relationships for these partial quantities: In the overlapping phase, when there are two overlapping requirements, the system distributes the receipt quantity of a discrete receipt, for example, to the overlapping requirements, by assigning a partial quantity alternately to the requirements. Accordingly, two overlapping receipts in the overlapping phase supply a discrete requirement alternately with partial quantities. dependencies Concurrent pegging is not relevant to fixed pegging. To determine the partial quantities in the overlapping phase you must specify the duration of the time interval in the field next to the indicator. For performance reasons you should not make the duration too small; a duration in seconds does not make sense.

ER10

DEFINITION USE This field is only relevant if you have set the concurrent pegging indicator. The system splits the overlapping phase of overlapping requirements and receipts into time intervals of this duration, and splits the requirements or receipt quantity, required or made available in the overlapping phase, into corresponding partial quantities.

req_max_underdelivery

Maximum Permitted Underdelivery of a Requirement (Percent)/sapapo/uneto

dec/ 3/ 1

ES9

4

ES10

DEFINITION Percentage value that specifies by how much the supply quantity is permitted to fall below the requirement quantity of a requirements element. Example: If it is permissible for 10 percent of the requirement quantity not to be fulfilled, you enter 10. Therefore, when there is a requirement quantity of 100 pieces, the maximum tolerated underdelivery is 10 pieces, which means, a minimum of 90 pieces should be delivered. USE The use of the delivery tolerances depends upon whether you have set the Use Entire Stock or Use Entire Receipt indicators, as follows: If you have not set the Use Entire Stock or Use Entire Receipt indicators, the delivery tolerances are relevant to the generation of quantity alerts for requirements. If the total quantity of the stock and receipt elements assigned to a requirement element is outside the tolerance range, the system generates an undercoverage alert or an overcoverage alert for a requirement. Since in the case of dynamic pegging the system may only ever assign a maximum of one total receipt quantity which covers the requirement, the overdelivery tolerance is not relevant here. If you have set the Use Entire Stock or Use Entire Receipt indicators, the system must assign the complete quantity of a stock or receipt element to a requirement element. The overdelivery tolerance influences the dynamic pegging for these elements, which may only have one pegging relationship. The system may also assign such a stock or receipt element to a requirement element if an overdelivery within the context of the overdelivery tolerance is generated as a result. In this case - as above - the underdelivery tolerance is only significant with regard to the generation of undercoverage alerts. Example: The tolerance range of a requirement element with a requirement quantity of 100 pc is between 90 and 110 pc. Receipt elements with a total receipt quantity of 90 pc have already been assigned to the requirement element. There is thus an undercoverage situation within the context of the underdelivery tolerance, for which the system will not generate an alert but which it will nevertheless try to avoid in dynamic pegging. The system may still assign a receipt element that is to be completely consumed with a receipt quantity of 20 pieces. The system does not take delivery tolerances into account in the planning (for example, in the net requirements calculation) The delivery tolerances relate to a requirement element. For example, in the case of a sales order, the delivery tolerance relates to a schedule line - not to an item. You specify whether the system displays quantity alerts in the PP/DS alert profile.

req_max_overdelivery early_rcpt_alert_thold

Maximum Permitted Overdelivery of a Requirement (Percent) Alert threshold for early receipts/sapapo/ueeto /sapapo/dm_pegging_futur_alert

dec/ 3/ 1 dec/ 11/ 0

EU8


ET9

4

EU9

10

ET10

DEFINITION The tolerance level in percent of how much more of an order quantity may be delivered. use Delivery tolerances are often required in a make-to-order environment where every customer has different requirements. If the batch size is slighty larger than the order quantity, the customer may tolerate, for example, 5% more than they ordered.

EU10

use The system creates a date/time alert for a fixed or a dynamic pegging relationship if the earliness exceeds the alert threshold; that is, if the availability date/time is earlier than the specified timeframe before the requirements date. You specify the timeframe in the format HHH.HHH:MM (hours:minutes). Example: 1.000:10 means 1000 hours and 10 minutes, 20:20 means 20 hours and 20 minutes. If you do not specify a value, the system uses the value 100000:00. Therefore, the system only creates an alert if an availability date/time is more than 100,000 hours before the requirements date. dependencies To enable the system to display the alerts, you must use an appropriate PP/DS alert profile in interactive planning. To be able to see date/time alerts in dynamic pegging, the alert thresholds should be within the pegging interval. You should note that the alert thresholds for earliness and lateness are used in the calculation of the days' supply. You can use the Business Add-In (BAdI) /SAPAPO/RRP_COVPARAM to influence the way in which the days' supply is calculated.

late_rcpt_alert_thold use_entire_receipt_flag

Alert threshold for delayed receipts Use/Consume Entire Quantity of a Receipt Element/sapapo/dm_pegging_past_alert /sapapo/ges_mng_use

dec/ 11/ 0 char/ 1/

EV8


EV9

10

EW9

1

EV10

use The system creates a date/time alert for a fixed or a dynamic pegging relationship, if the delay exceeds the alert threshold; that is, if the availability date/time is later than the specified timeframe after the requirements date. You specify the timeframe in the format HHH.HHH:MM (hours:minutes). Example: 1.000:10 means 1000 hours and 10 minutes, 20:20 means 20 hours and 20 minutes. If you do not specify a value, the system uses the value 0. Therefore, the system creates an alert if the availability date/time is after the requirements date. dependencies To enable the system to display the alerts, you must use an appropriate PP/DS alert profile in interactive planning. To be able to see date/time alerts in dynamic pegging, the alert thresholds should be within the pegging interval. You should note that the alert thresholds for earliness and lateness are used in the calculation of the days' supply. You can use the Business Add-In (BAdI) /SAPAPO/RRP_COVPARAM to influence the way in which the days' supply is calculated.

EW10

USE If you set this indicator, the system may assign a receipt element to just one requirement element for the product during dynamic pegging. The requirement element must thus completely consume the receipt element. dependencies See delivery tolerances.

use_entire_stock_flag no_inspection_stock_flag

Use/Consume Entire Quantity of a Stock Element Stock in Quality Inspection not Available/sapapo/ges_bst_use /sapapo/nopeg_st_quali

char/ 1/ char/ 1/

EY6

X Yes No

EX9

1

EY9

1

EX10

DEFINITION Defines that all stock is to be used in full, that is, the full amount of a stock element must be pegged to a requirement element; no partial quantities are permitted. USE A requirement may be covered by several stock elements, but these stock elements must be used in full. This helps to ensure that each batch is fully consumed. Example You have a requirement of 180 pieces. You have two existing stock elements of 100 pieces each. The system only uses one of these stock elements and creates a new receipt element for the remaining 80 pieces. DEPENDENCIES During this process, minimum and maximum lot sizes are taken into account, as well as over- and underdelivery tolerances.

EY10

DEFINITION USE If you set this indicator, stocks of the type Stock in Quality Inspection count as unavailable in Production Planning and Detailed Scheduling and in Capable-To-Match. The system does not take such stocks into account in the net requirements calculation and in dynamic pegging. DEPENDENCIES EXAMPLE HINTS

restricted_stock_flag blocked_stock_flag

Restricted-Use Stock is Available Blocked Stock is Available/sapapo/peg_st_restr /sapapo/peg_st_blocked

char/ 1/ char/ 1/

EZ6

X Yes No

FA6

X Yes No

EZ9

1

FA9

1

stock_trf_loc_flag no_stock_trf_subloc_flag

Stock in Transfer Between Locations Available Stock in Transfer Between Sublocations not Available/sapapo/peg_stock_transf_loc /sapapo/nopeg_stock_tr_subloc

char/ 1/ char/ 1/

FB6

X Yes No

FC6

X Yes No

FB9

1

FC9

1

FC10

DEFINITION USE If you set this indicator, stocks of the type Stock in Transfer Between Sublocations count as unavailable in Production Planning and Detailed Scheduling and in Capable-To-Match. The system does not take such stocks into account in the net requirements calculation and in dynamic pegging. DEPENDENCIES EXAMPLE HINTS

single_tolerance_max single_tolerance_min alert_relevance

Plus Percentage Tolerance Minus Percentage Tolerance Alert Relevance of Product/sapapo/tolprpl /sapapo/tolprmi /sapapo/get_alerts_for_prod

dec/ 3/ 1 dec/ 3/ 1 char/ 1/

FF6

Determine Direct Alerts, Relevant to Network Alerts 1 Determine Direct Alerts, Not Relevant to Network Alerts 2 Do Not Determine Any Alerts

FD9

4

FE9

4

FF9

1

FD10

DEFINITION Indicates the maximum permitted surplus of the individual product tolerance in the requirement element as a percentage. USE If a characteristic means that a requirement quantity is subdivided into individual quantities, you can define the maximum percentage by which the individual partial quantity can be exceeded. DEPENDENCIES This value is defined in the Overdelivery tolerance charcteristic (controlled in Customizing) and is transferred to the product at location level (individual product tolerance) via the CIF interface. In APO, this permitted surplus is taken into account in the individual nodes in length-based planning. EXAMPLE

FE10

DEFINITION Indicates the maximum permitted shortage of the individual product tolerance in the requirement element as a percentage. USE If characteristic means that a requirement quantity is subdivided into individual quantities, you can define here the maximum percentage by which the individual partial quantity is not reached. DEPENDENCIES This value is defined in the Underdelivery tolerance characteristic (controlled in Customizing) and transferred to the the product at location level (individual product tolerance) via the CIF interface. In APO, this permitted shortage is taken into consideration in the inidividual input nodes in length-based planning. EXAMPLE

FF10

DEFINITION USE In this field, you specify whether: The system determines direct alerts for a requirement or a receipt of a product The product is relevant to network alerts If a product is relevant to network alerts, the system evaluates the direct alerts that it determines for this product for receipts or requirements at the superordinate levels of the pegging structure as well. You can hide alerts for less critical components and thus: Increase the clarity and transparency of the network alerts Improve performance If you choose the option Do Not Determine Any Alerts, the system will not determine any direct alerts for the product. The product is thus also not relevant with regard to network alerts. DEPENDENCIES You specify whether and which alerts are actually displayed by the system in the planning interface or in the Alert Monitor in the PP/DS alert profile that you use for planning.

lot_size_profile lot_size_uom

External key: Lot size profile / days' supply profile Unit of measure of lot size/sapapo/lszky /sapapo/lsuom

char/ 10/ unit/ 3/

FH8


FG9

10

FH9

3

FG10

DEFINITION The lot size profile defines which lot-sizing procedure should be used in production planning calculation. Use If you wish to enter the same lot-size procedure and additional restrictions (where applicable) for many materials, for example minimum or maximum lot-sizes or a rounding value, you can define these in a lot size profile. The settings defined in the lot-size profile will be considered in the material master record, but can no longer be changed in the material master record.

FH10

DEFINITION Indicates the valid unit of measure. USE The following options exist: No lot size units maintained: The base unit of measure (BME) maintained for the product applies. A unit of measure (alternative or base unit of measure) can be maintained which can be converted to the base UoM. DEPENDENCIES If you enter an alternative unit of measure, the conversion to the base UoM must be maintained on the tab Units of Measure. The alternative units of measure must be able to be converted to the base UoM for the product, as otherwise the unit will not be accepted. The conversion from alternative to base unit of measure is dependent on the material. EXAMPLE The alternative unit of measure is kilogram (kg). The base unit of measure is piece (pc). 5kg correspond to 3 pieces.

lot_size_uom_iso lot_size_calc_procedure

ISO code for unit of measurement Procedure for Lot Size Calculationisocd_unit /sapapo/sl_lsz_range

char/ 3/ char/ 1/

FJ6

E Lot-for-lot order quantity F Fixed lot size P Periodic lot size R Lot size at reorder point

FI8

Valuetable: T006I

FI9

3

FJ9

1

FI10


FJ10

DEFINITION Determines that the defined target days' supply is used when calculating lot size.

lot_size_calculation_flag last_lot_exact_flag fixed_lot_size period_type

Lot-Size Calculation in Make-to-Order Production Last Lot Exact Fixed Lot Size Period Type/sapapo/lgknd /sapapo/lastl /sapapo/bstfe /sapapo/pervr

char/ 1/ char/ 1/ quan/ 13/ 3 char/ 1/

FK6

X Selected Not selected

FL6

X Selected Not selected

FN6

H Hour D Day W Week M Month J Jun Q Quarter K Planning Calendar B BAdI

FM8

Reference Table: BAPI10001LOCPRDVERS2 Reference Field: LOT_SIZE_UOM

FK9

1

FL9

1

FM9

17

FN9

1

FK10

DEFINITION Defines that the lot-sizing procedure you have selected will also be used for make-to-order and engineer-to-order production. If you do not set the indicator, the lot-for-lot order quantity procedure will always be used for make-to-order and engineer-to-order production. Additional restrictions, such as minimum/maximum lot size or rounding values, are also not taken into account. In Supply Network Planning (SNP), this field is not taken into account.

FL10

DEFINITION USE This indicator is only relevant for Production Planning and Detailed Scheduling (PP/DS), and not for Supply Network Planning and Capable-to-Match. If you set this indicator, the system creates the last receipt within a specific time period, not according to the configured lot-sizing procedures and parameters, but using a reduced quantity, so that the available quantity at the end of the time period is 0. The time period is defined as follows: In the case of a product that is not interchangeable, the time period is the PP/DS horizon. For an interchangeable product, which belongs to a supersession chain, the time period is the validity period of this product. However, the prerequisite for the reduction of the receipt quantity is, in this case, that the validity period does not last beyond the PP/DS horizon. If the validity period is longer, the system assumes that there are more requirements for the product after the end of the PP/DS horizon that require regular receipts in order for them to be covered. By setting the indicator, you can prevent the system creating too large a receipt for a product that is to be discontinued, which leads to surplus stock. Depending on the use-up strategy, this stock would no longer be usable after the discontinuation date or use-up date and would therefore represent scrap. If you do not set the indicator, the system calculates the receipt quantities according to the configured lot-sizing procedures and parameters. The indicator is not relevant for PP/DS heuristics that execute procurement planning using the reorder point method. For interchangeable products that you plan using this method, you have to adjust the reorder point, or set it to zero, before the discontinuation date. DEPENDENCIES EXAMPLE NOTE

FM10

DEFINITION Quantity in lot size unit of measure that is to be ordered or produced for material shortages. VORGEHEN If the material shortage is less than the fixed lot size, exactly the fixed lot size is ordered or produced. If the material shortage is greater than the fixed lot size, a multiple of the fixed lot size is procured. In this case, the system creates several orders.

FN10

DEFINITION Defines the type of period, for example, day, week, month, and so on, to be used for period lot-sizing.

number_of_periods planning_calendar reorder_point_procedure

Number of Periods Planning Calendar for Periodic Lot Sizing Procedure Reorder Point Method/sapapo/rrp_peraz /sapapo/lot_tstrid /sapapo/reord_method

dec/ 3/ 0 char/ 10/ char/ 1/

FQ6

1 Reorder stock from location product master 2 Reorder supply from location product master 3 Maximum from MB and MR from location product master 4 Reorder point (time-dependent maintenance) 5 Reporting Days' of Supply (time-depnedent maintenance) 6 Maximum from MB and MR (time-dependent maintenance)

FP8

Valuetable: TTSTR

FO9

4

FP9

10

FQ9

1

FO10

DEFINITION Defines the number of periods that are to be included in the short-term, medium-term or long-term horizon. use You can define three horizons in which a different number of periods, type of period and lot-sizing procedure can be defined for each of the three horizons. example You could define the following horzions: Short-term = 5 days using lot-for-lot procedure Medium-term = 2 weeks using period lot-sizing (weekly lot size) Long-term = All requirements not covered by other horizons are covered here using period lot-sizing (monthly lot size)) In this example, planning becomes more detailed in the short-term.

FP10

DEFINITION use For the periodic lot-sizing procedure, use an APO standard time stream as a planning calendar. This field is not taken into account in Supply Network Planning (SNP).

FQ10

DEFINITION USE You use this to specify the reorder point method that you want to use for planning the product. Use in Production Planning and Detailed Scheduling (PP/DS) If you want to use a reorder point method in Production Planning and Detailed Scheduling (PP/DS) for planning, you have to use the heuristic for planning standard lots SAP_PP_002 (algorithm /SAPAPO/HEU_PLAN_STANDARDLOT). For this heuristic, you can only use reorder point method 1 and reorder point method 2, but not reorder point methods 3 to 6. Use in Supply Network Planning (SNP) The reorder point method that you have chosen is taken into account during heuristic-based planning only (and not during optimization-based planning ). Depending on which method was chosen, the system determines the reorder point using the value from the location product master or the one entered in interactive Supply Network Planning (time-based maintenance), or derives it from the reorder days' supply. The SNP heuristic regards the reorder point as a threshold value for available stock on hand, which should not be fallen below during planning. dependencies

reorder_days_supply minimum_lot_size maximum_lot_size

Reorder Days' Supply (in Workdays) Minimum Lot Size Maximum Lot Size/sapapo/reord_dur /sapapo/bstmi /sapapo/bstma

dec/ 11/ 0 quan/ 13/ 3 quan/ 13/ 3

FR8


FS8


FT8


FR9

10

FS9

17

FT9

17

FR10

DEFINITION USE Use in Production Planning and Detailed Scheduling (PP/DS) Specify the reorder days' supply if you have defined reorder point method 2 for the location product. Use in Supply Network Planning (SNP) The SNP heuristic takes the reorder days' supply into account if you have chosen reorder point method 2 or 3. The SNP optimizer ignores the reorder days' supply.

FS10

DEFINITION Quantity in lot size unit of measure that must not be fallen below during procurement. USE The system considers the minimum lot size as an additional constraint when calculating lot sizes for orders. The lot size of the individual orders is not allowed to be smaller than this value. Use in Supply Network Planning (SNP) In heuristic-based planning , this value specifies the minimum quantity for each order. The minimum lot size specified at the production process model (PPM) only refers to the validity of the PPM and does not overwrite the value given here. In optimization-based planning , this value specifies the minimum quantity in each order and period. If this value is larger than the minimum lot size defined at the PPM, the SNP optimizer takes into account the value given here, if not, it uses the value from the PPM. The deployment heuristic and the Transport Load Builder (TLB) do not take the minimum lot size into account. DEPENDENCIES If the fixed lot size method is being used, the system ignores the minimum lot size. You have to choose the discrete optimization method in the SNP optimizer profile and enter a discretization horizon in the Minimum PPM Lot Size field of the Discrete Constraints tab page for the SNP optimizer to be able to take into account the minimum lot size specified here. EXAMPLE

FT10

DEFINITION Quantity in lot size unit of measure that must not be exceeded during procurement. USE The system considers the maximum lot size as an additional constraint when calculating lot sizes for orders. The lot size of the individual orders is not allowed to be greater than this value. Use in Supply Network Planning (SNP) In heuristic-based planning , this value specifies the maximum quantity for each order. If required, the system creates multiple orders with this maximum quantity. The maximum lot size defined in the production process model (PPM) only refers to the validity of the PPM and does not overwrite the value given here. In optimization-based planning, this value is ignored. The SNP optimizer only considers the value defined in the PPM. Deployment Optimization and the Transport Load Builder (TLB) do not consider the maximum lot size.

target_stock_level_method assembly_scrap rounding_value

Target Stock Level Method Assembly Scrap in Percent Rounding Value for Purchase Order Quantity/sapapo/target_method /sapapo/ausss /sapapo/bstrf

char/ 1/ dec/ 5/ 2 quan/ 13/ 3

FU6

Target days' supply from product master 1 Target days' supply (time-dependent maintenance) 2 Target stock level (time-dependent maintenance) 3 Maximum of TSL/TDS (time-dependent maintenance) 4 Target stock level equals maximum stock level + SS 5 Maximum of Maximum Stock Level/TS (product master) 6 Sum of MAXIMUM Stock LEVEL/TS (product master) 7 No target stock level

FW8


FU9

1

FV9

6

FW9

17

FU10

DEFINITION USE Use in Supply Network Planning (SNP) The target stock level method is only considered during heuristic-based planning (and not optimization-based planning ). The target stock level represents a value that is to be reached by the available stock on hand during planning. The following methods are available: No entry: The system derives the target stock level from the target days' supply that is specified in the location product master. 1-3: The system derives the target stock level from the target days' supply specified in interactive SNP (time-based maintenance), or uses the target stock level that is entered there. 4-6: To determine the target stock level, the system uses the value specified in the Maximum Stock Level field in conjunction with the safety stock or target days' supply specified in the location product master. 7: The system does not take any target stock level into account. Use in Production Planning and Detailed Scheduling (PP/DS) You can use the following target stock level methods in PP/DS: No entry,,Target days' supply from product master 4,,Target stock level equals maximum stock level + safety stock 5,,Maximum from maximum stock level/target days' supply (product master) 6,,Total from maximum stock level/target days' supply (product master) 7,,No target stock level To plan location products using target stock level methods, use the standard heuristic SAP_PP_002 (planning of standard lot sizes). DEPENDENCIES You can be informed by alerts when the target days' supply has not been reached or has been exceeded. To do this, you must select the Target Days' Supply not Reached and Target Days' Supply Exceeded alerts in the Alert Monitor and/or Alert Profile. (For PP/DS: Tab page PP/DS -> Stock Alerts, for SNP: Tab page SDP -> Dynamic Alerts) EXAMPLE

FV10

DEFINITION Scrap, as a percentage, that is produced during the in-house production of a product. The percentage of assembly scrap is related to the total quantity produced by an order, that is, to the required yield plus the scrap quantity. USE During manual creation of an order and during lot size calculation, the system uses the required yield and the assembly scrap to calculate the total quantity, as follows: Total quantity = yield x 100% / (100% - scrap in %) dependencies The following increase with the total quantity: The quantity of product components required The net duration of activities, with quantity dependent processing time The resource consumption of activities, with quantity dependent resource consumption example The required yield is 100 pieces. You enter an assembly scrap of 20%. This results in: Total quantity = 100 pieces 100% / (100% - 80%) = 100 pieces / 0.8 = 125 pieces. Scrap = 25 pieces

FW10

DEFINITION The system rounds the procurement quantity up to a multiple of this value. USE Use in Supply Network Planning (SNP) The rounding value is considered in both heuristic-based planning and optimization-based planning. The following applies for optimization-based planning: If you do not enter a rounding value or enter the value 0, the system uses the rounding logic of the production process model (PPM). This means that the system uses the value that you defined at the PPM for variable material consumption of the output product as a basis for the rounding value. In Supply Network Planning (SNP) and in the Inventory Collaboration Hub (ICH), the Transport Load Builder (TLB) also uses this rounding value to build transport loads. However, the TLB first considers the value that you have defined in the transportation lane, that is, in the lot sizing profile (SNP) or the transportation guideline set (SAP ICH) specified there. If no value has been defined there, the TLB uses the value entered here, or the value 1. DEPENDENCIES If you specified a rounding profile in the location product master, the system uses this profile instead of the rounding value. The SNP optimizer, deployment, and the Transport Load Builder (TLB) all ignore the rounding profile. The rounding value is not considered in connection with the fixed lot size method. You have to choose the discrete optimization method in the SNP optimizer profile and enter a discretization horizon in the Integral PPMs field of the Discrete Constraint tab page for the SNP optimizer to be able to take the rounding value into account. So that the SNP-TLB can use the rounding value, you must set the corresponding indicator in Customizing for SNP under Basic Settings -> Maintain Global SNP Settings. Otherwise the SNP-TLB uses only the rounding value from the transportation lane. The deployment heuristic rounds values down.

rounding_profile target_days_supply safety_days_supply availability_calculation

Rounding Profile Target Days' Supply in Workdays Safety Days' Supply Use Period Factor/sapapo/rdprf /sapapo/target_dur /sapapo/svtty /sapapo/rrp_req_cover_flag

char/ 8/ dec/ 11/ 0 dec/ 11/ 0 char/ 1/

GA6

Application-Dependent Standard X Availability from Period Duration and Period Factor

FX8

Valuetable: /SAPAPO/RDPR

FY8


FZ8


FX9

8

FY9

10

FZ9

10

GA9

1

FX10

DEFINITION Key that the system uses to adjust the order proposal quantity to deliverable units. USE WHAT_TO_DO In Customizing, enter a threshold value for each deliverable unit. Once this value is reached, the system rounds up to the next value: If the requirement or demand value exceeds the first threshold value, the system always rounds up to the next multiple of the rounding value of the level found. If the requirement value falls below the first threshold value, the system copies the original requirement value. EXAMPLES A material's base unit of measure is 1 unit; the purchase order is to be delivered in layers (1 layer corresponds to 5 units) or in pallets (1 pallet corresponds to 8 layers which contains 40 units). You maintain the profile as follows: From a requirement of 2 units, the system is to round up to 5; from a requirement of 32 units, the system is to round up to 40. This results in the following order proposal quantities: Requirement from 1 -> 1,,,,requirement from 31 -> 35 Requirement from 2 -> 5,,,,requirement from 32 -> 40 Requirement from 6 -> 10,,requirement from 74 -> 80 Requirement from 7 -> 10 DEPENDENCIES If you do not enter a rounding profile, the system uses the rounding value entered in the material master record. The rounding profile is not considered in connection with the fixed lot size lot size method. The system also considers the minimum and maximum lot sizes defined in the location product master. In Supply Network Planning (SNP), the rounding profile is only considered during heuristic-based planning and not during optimization-based planning . Deployment and the Transport Load Builder do not consider the rounding profile either.

FY10

DEFINITION USE Use in Production Planning and Detailed Scheduling (PP/DS) and Supply Network Planning (SNP) The PP/DS standard heuristic SAP_PP_002 (Planning of Standard Lots) and the SNP heuristic take into account the target days' supply if you have selected the target stock level method Target Days' Supply from Product Master (' '), Maximum from Maximum Stock Level/Target Days' Supply (5) or Total from Maximum Stock Level/Target Days' Supply (6). DEPENDENCIES The SNP optimizer ignores the target days' supply. EXAMPLE

FZ10

DEFINITION USE Supply Network Planning (SNP), Capable-to-Match (CTM), and Production Planning and Detailed Scheduling (PP/DS) can take into account the safety days' supply during planning with the non-period-based (static) safety stock methods SZ and SM. Use in SNP In SNP, the safety days' supply specifies the number of workdays over which the system has to take into account future demands when planning safety stock. For example, if the safety days' supply is three days, the safety stock has to cover the demands for the next three workdays. SNP also takes into account decimal places (a safety days' supply of 2.5 days, for instance). The system uses the location's shipping calendar to determine the working times. With the period-based (dynamic) safety stock methods MZ and MM, you do not enter the safety days' supply in the location product master; instead, you enter it directly in the planning table for interactive planning in the relevant periods. With safety stock method MM, the SNP optimizer only takes account of independent requirements, and dependent demands and distribution demands that are caused by fixed orders since these demands and demand locations are already known before the optimization run. Use in CTM CTM uses the safety days' supply as a safety time between the availability date of a receipt element and the requirements date of the requirements element that is to be covered by this receipt element. The system is only permitted to use an existing fixed receipt element to cover the requirement if the availability date falls on the specified number of calendar days before the requirements date. The same applies if the system creates a new receipt element. If you enter a value that includes decimal places for the safety days' supply, the system rounds this value up to the nearest integer. Use in PP/DS In PP/DS, only procurement planning heuristics take the safety days' supply into account. Procurement planning heuristics use the safety days' supply as a safety time. A safety time ensures that a requirement is not fulfilled on the exact date and time required, but at an earlier point in time. This means that appropriately early receipts should be used or generated during planning. A procurement planning heuristic considers the safety time by subtracting the safety time from every requirements date and time at the start of a planning process. This means that it moves the requirements date and time to a point in time that is appropriately earlier. The net requirements calculation is made on the basis of the requirements date and time that was brought forward. When recreating receipt elements for an unfulfilled requirement, the requirements date that has been brought forward is the desired availability date. You specify the safety days' supply as a number of workdays, where it is possible to have up to two decimal places and a workday equals 24 working hours. For example, if you specify 0.5, the safety time is 12 hours. The system uses the location's production calendar to determine the working times. EXAMPLE DEPENDENCIES You specify the safety stock method in the SStk Method field.

GA10

DEFINITION USE You use this indicator to define how the system determines the desired availability date/time of the receipts that should cover the requirements in a period. The indicator is relevant for period-based planning and is thus relevant for the following applications: Heuristic in Supply Network Planning (SNP) Period lot-sizing procedure in Production Planning and Detailed Scheduling (PP/DS) Usage in the SNP Heuristic The system only takes into account the Use Period Factor indicator if you have not specified a period factor in the production process model or in the transportation lane. (If you have specified a period factor in the PPM or in the transportation lane, the system uses this period factor to determine the availability date/time.) The system evaluates the Use Period Factor indicator as follows: If you do not set the indicator, the desired availability date/time of the receipt elements is in the middle of the period, corresponding to a period factor of 0.5. Within daily buckets, the system sets the availability time automatically to 12:00. If you set the indicator and do not enter a value in the Period Factor field, the system also sets the availability date/time to the middle of the period. If you specify a period factor, the system uses the period factor to determine the availability date/time. Usage in Period Lot-Sizing Procedure in PP/DS If you do not set the Use Period Factor indicator, the desired availability date/time of the receipt elements is the first requirements date/time in the period. If you set the Use Period Factor indicator, the system calculates the desired availability date/time from the period duration, defined by the period type, the number of periods of the period lot-sizing procedure, and the period factor from the Period Factor field. The date/time at which the system actually schedules a receipt element depends on further factors, such as the planning time fence, the strategy settings that are being used for detailed scheduling, or the resource utilization.

period_factor safety_stock

Period Factor for Calculating the Availability Date/Time Safety Stock/sapapo/rrp_req_cover_type /sapapo/saftyc

dec/ 4/ 3 quan/ 15/ 3

GB6

0.000 Factor for Availability Date Within the Period

GC8


GB9

5

GC9

19

GB10

DEFINITION Factor used by the system to calculate the availability date/time of a receipt element within a time period (bucket). USE The system determines the exact availability date/time of the receipt elements within a period, by adding a time interval (that it gets by multiplying the period factor with the period length) to the start time of the period. You can enter a factor between 0 and 1, where 0 is the start of the period, 0.5 the middle, and 1 the end of the period. When calculating the availability date/time, the system takes into consideration all weekdays, meaning that it does not take into consideration any days that have been defined as non-workdays in the calendars. The following applications can take the period factor into account: Heuristic in Supply Network Planning (SNP) The SNP optimizer does not consider any period factor. Period lot-sizing procedure in Production Planning and Detailed Scheduling (PP/DS) Usage in the SNP Heuristic The system uses the period factor to calculate the availability date . It sets the availability time automatically to 12:00 within daily buckets. The following period factors are relevant for the SNP heuristic: Period factor in the location product master In order that the SNP heuristic can take the period factor into consideration, you have to set the Use Period Factor indicator. If you do not set the indicator, the system always uses the standard value 0.5 for the period factor. Period factor in the production process model or in the transportation lane If you have defined a value for the Period Factor for the SNP heuristic in a production process model (PPM) or in a transportation lane, the system first considers this value when calculating the availability date/time. The period factor in the production process model is only relevant for in-house production orders, while the period factor in the transportation lane is only relevant for external procurement orders. If, in the PPM or in the transportation lane you have not defined a value, the system checks if you have set the Period Factor indicator in the location product master. If this is the case, the system takes the value defined in the Period Factor field of the location product master into consideration. If neither parameter has been maintained in the location product master, the system uses the standard value 0.5, meaning that it sets the availability date/time to the middle of the period. Usage in the PP/DS Period Lot-Sizing Procedure In order that PP/DS can consider the period factor from the location product master in the period lot-sizing procedure, you have to set the Use Period Factor indicator. The system calculates the availability date/time from the period duration, to the exact second. If , for example, you specify 0.75 for the period factor, for a period duration of one day, the availability time is 18:00. The period factor in the production process model or in the transportation lane is not relevant to PP/DS. EXAMPLE

GC10

DEFINITION Safety Stock in Base Unit of Measure. DEPENDENCIES The system takes the safety stock into account only if you have also specified a safety stock (SS) method. You can choose to be informed by alert when the stock falls below the safety stock level. To enable this you must select the alert Stock Fallen Below Safety Stock Level in the Alert Monitor or alert profile.

safty_stock_calc_method reorder_point maximum_stock_level service_level

Method for Calculating Safety Stock Reorder Point Maximum Stock Level Service level/sapapo/msdp_sb_method /sapapo/reordc /sapapo/maxstockc /sapapo/lgrad

char/ 2/ quan/ 15/ 3 quan/ 15/ 3 dec/ 3/ 1

GD6

No Safety Stock SB Safety Stock from Location Product Master SZ Safety Days' Supply from Location Product Master SM Max.of Safety Stock and Safety Days'Sup.from Loc.Prod.Master AT Alpha Service Level and Reorder Cycle Method AS Alpha Service Level and Reorder Point Method BT Beta Service Level and Reorder Cycle Method BS Beta Service Level and Reorder Point Method MZ Safety Days' Supply (Time-Based Maintenance) MB Safety Stock (Time-Based Maintenance) MM Max.of Safety Stock and Safety Days' Sup.(Time-Based Maint.)

GE8


GF8


GD9

2

GE9

19

GF9

19

GG9

4

GD10

DEFINITION USE There are various safety stock calculation methods: Standard methods Extended methods Standard Methods You use these methods to define the amount of safety stock and the safety days' supply in a direct and simple manner. Both of these parameters can be defined as period-based or not period-based. You can define the parameters that are not period-based directly in the location product master (on the Lot Size tab page). You define the parameters that are period-based in interactive Supply Network Planning. ,,,,,,,,,,,,,,Period-based,,,,,,,,,,,,,,Not period-based Safety stock,,,,,,,,,,,,,,MB,,,,,,,,,,,,,,SB Safety days' supply,,,,,,,,,,,,,,MZ,,,,,,,,,,,,,,SZ Maximum from both,,,,,,,,,,,,,,MM,,,,,,,,,,,,,,SM Extended Methods The system uses these methods to calculate period-based safety stock based on a forecast error and the service level specified. There are four different methods available depending on the lot-sizing procedure and service level chosen: ,,,,,,,,,,Reorder point method,,,,,,,,,,Reorder cycle method Alpha service level,,,,,,,,,,AS,,,,,,,,,,AT Beta service level,,,,,,,,,,BS,,,,,,,,,,BT For more information about Alpha and Beta service levels, see the F1 help for the Service level (%) field. In the reorder cycle method, it is indicated that purchase orders can only be made for all t periods. In the reorder point method, a purchase order is generated within the framework of SNP planning depending on stock level. DEPENDENCIES It is a prerequisite of the extended safety stock calculation methods that there must be regular demand (no sporadic demand). It is also required that stock shortfalls are eventually delivered (backorder case). With safety stock method MM, the optimizer only takes into account independent requirements, and dependent demands and distribution demands that result from fixed orders since these demands and demand locations are already known before the optimization run. EXAMPLE

GE10

DEFINITION Reorder Point in Base Unit of Measure. USE Use in Production Planning and Detailed Scheduling (PP/DS) Specify the reorder point if: You wish to use reorder point method 1 to plan the location product To plan location products with reorder point method 1, use the standard heuristic for the planning of standard lot sizes SAP_PP_002 (algorithm /SAPAPO/HEU_PLAN_STANDARDLOTS). You wish to plan with the standard heuristic for reorder point planning SAP_PP_007 (algorithm /SAPAPO/HEU_REORDER_POINT_PLAN) If the standard heuristic is used ... Use in Supply Network Planning (SNP) The SNP heuristic takes the reorder point into account if you have chosen reorder point method 1 or 3. The reorder point represents a threshold value for available stock on hand, which should not be fallen below during planning. The SNP optimizer ignores the reorder point. DEPENDENCIES

GF10

DEFINITION Maximum Stock Level in the Base Unit of Measure. USE Use in Production Planning and Detailed Scheduling (PP/DS) In Production Planning and Detailed Scheduling (PP/DS), you can use the maximum stock level for reorder point planning with standard heuristic SAP_PP_007 (algorithm: /SAPAPO/HEU_REORDER_POINT_PLAN). If stock falls below this level, this heuristic can create procurement proposals to replenish the stock up to the maximum level. In heuristic-based planning with the standard heuristic SAP_PP_002 (Planning of Standard Lots), the maximum stock level is taken into account if you have chosen the target stock level method 4, 5 or 6. With these methods, the system determines the target stock level on the basis of the maximum stock level (corresponds to the prod. storage capacity in the input help) in combination with the safety stock or the target days' supply. Use in Supply Network Planning (SNP) In Supply Network Planning (SNP), you can use the maximum stock level to specify a product-specific upper stock bound for optimization-based planning . The SNP optimizer regards the upper stock bound as a soft constraint that can be violated subject to the calculation of penalty costs. These penalty costs are specified by the optimizer - they cannot be set in the master data. Heuristic-based planning takes account of the maximum stock level if you have selected target stock level methods 4, 5, or 6. In these methods, the system determines the target stock level using the value given in the Maximum Stock Level field (corresponds to the "Prod. Storage Capacity" in the F4 input help) combined with the safety stock, or with the days' supply given in interactive SNP planning. DEPENDENCIES The SNP optimizer takes the upper bounds for stock into account during planning only if you have set the Maximum Product-Specific Quantity Stored indicator on the General Constraints tab page in the SNP optimization profile. If you wish to set a time-based upper bound for stock for optimization-based planning in SNP, you can define it as a time-based constraint in interactive Supply Network Planning (SNP standard planning book 9ATSOPT). If the target stock level is not reached or exceeded, you can be informed accordingly via an alert. For this to occur, you must choose the alerts Target Days' Supply Not Reached and Target Days' Supply Exceeded in the Alert Monitor or alert profile. (For PP/DS: PP/DS -> Inventory Alerts tab page, for SNP: SDP -> Dynamic Alerts tab page).

GG10

DEFINITION Percentage specifying the proportion of the requirement to be covered by the warehouse stock. USE The system uses the service level to calculate the safety stock. The higher the service level, the higher will be the safety stock calculated by the system to compensate for additional consumption or delays in delivery.

planning_procedure part_of_package_flag

PP Planning Procedure Location Product is Part of a Planning Package/sapapo/rrp_planning_type /sapapo/rrp_package_flag

char/ 1/ char/ 1/

2222

2222

22222

2222

222

222

GI6

X TRUE FALSE

GH8

Valuetable: /SAPAPO/RRPTYPE

GH9

1

GI9

1

GH10

DEFINITION Defines for each planning-relevant event that can occur for a location product, which action is executed by Production Planning and Detailed Scheduling (PP/DS) in SAP APO if this event occurs. The PP planning procedure also determines, for customer requirements, whether the desired quantity or confirmed quantity of a schedule line is relevant for pegging. USE In the location product master, you assign a planning procedure to each location product that you want to plan in PP/DS. Planning procedures are named with keys 1 to 9 (SAP namespace) and A to Z (customer namespace). EXAMPLE A planning-relevant event is, for example, a goods movement for a product or a change in the product master. Possible actions by the SAP APO system are, for example, immediately calling up a product heuristic for the product, or creating a planning file entry. DEPENDENCIES

GI10

Defines that this product is to be planned as part of a planning package. A planning package groups together several products that are to be planned together using the same heuristic. Use Often products cannot be planned independently of one another. You use a planning package to define which products are to be planned together using which heuristic. For this purpose, special package heuristics are available. Example of these include: All products that are manufactured together in a production process (manufacture of co-products). This means that, if more is produced of one product, more will be produced of the other products automatically. All products that are procured from the same vendor. The vendor could grant a bonus if several products are procured from the same vendor. Several products load the same resource.

2222

22

222222

22222

222

222222

2222

planning_package planning_package_type heuristic

Planning Package to Which Product Belongs Planning Package Type Heuristic/sapapo/heur_package_id /sapapo/heur_object_type /sapapo/cdps_heur_id


GK8

Valuetable: /SAPAPO/RRPCUST2

GJ9

12

GK9

3

GL9

12

GJ10

DEFINITION USE This field displays the planning package to which the location product belongs. DEPENDENCIES EXAMPLE

GK10

DEFINITION Classification of a planning package. USE The system automatically classifies planning packages. Planning packages created manually in the location product master belong to planning package type 000, for example. Planning packages, which the system creates automatically for the products in a supersession chain, belong to type 001. Depending on the planning package type, you define Which heuristic the system uses by default in procurement planning to process a planning package If the assignment of a product to a planning package can be changed in planning package maintenance in the location product master DEPENDENCIES EXAMPLE

GL10

DEFINITION

plan_explosion bom_explosion_date opening_period

Plan Explosion Determination of the BOM Explosion Date Opening Period in Workdays/sapapo/whatbom mmrp_expldate_finder /sapapo/erhor

char/ 1/ char/ 1/ dec/ 11/ 0

GM6

The Default Value from Customizing is Used 2 Explode Production Process Model 3 Single Explosion of iPPE 4 Matrix Explosion of iPPE 5 Production Data Structure Generated from R/3 6 Length-Based Plan Explosion

GN6

N Use component requirements date as BOM explosion date O Use BOM explosion date from the order for the final product P Use valid-from date for comp. var. as the BOM explosion date M BOM explosion dte from order or valid-from dte for comp.var. Default value from Customizing

GO8


GM9

1

GN9

1

GO9

10

GM10

USE You use this field to specify which task list type (BOM and routing) the system uses to create receipts in Production Planning and Detailed Scheduling (PP/DS).

GN10

DEFINITION States which date the system is to use to explode the PVS/ BOM for an assembly and its components when planning in the SAP DI system (from DI 4.6C2). USE The indicator is valid only for components that you have indicated as always collective requirements, and whose requirements have been transferred to the SAP DI system for planning. You can use this indicator to ensure that The correct BOM/iPPE data is found. The explosion date is used in the SAP DI system to determine the valid iPPE data, or the valid material BOM for the assembly and its components. The correct historical status is determined for the variant. You can choose from the following options: The explosion date for BOMs and determining the valid components is the requirements date that is determined during the planning for installing the assembly or component. The explosion date for the assembly BOMs and determining the valid components is the BOM explosion date from the order for the end product. The explosion date for the assembly BOMs and determining the valid components is the valid-from date for the component variant. Example: You have defined Assembly 1, which is valid from 01.01.2000, and Assembly 2, which is valid from 07.01.2000, at the component variant in the PVS for the WHEEL node. If Assembly 1 was calculated by the matrix, the explosion date for Assembly 1 and its subordinate components would be 01.01.2000. This procedure gives the correct results only when you use the same change number for the subordinate BOM levels and the superior assembly. The explosion date is the date that lies furthest in the future. The system compares the valid-from date for the component variant with the BOM explosion date in the order for the final product. hinweis You set the indicator for determining the BOM explosion date in Customizing for the Rapid Planning Matrix. It is then valid for all products that you indicate as always collective requirements . You can also set the indicator in the product master for individual components. DEPENDENCIES When requirements calculated by the Rapid Planning Matrix have been transferred to the SAP DI system for further planning, the BOM explosion date that has been determined by the SAP APO is also transferred to the SAP DI system. In the SAP DI system, a BOM explosion number is created for each BOM explosion date. Requirements planning explodes all levels of the BOM or iPPE data for the assemblies, using the BOM explosion date transferred from the SAP APO. For this to happen, you must allow BOM explosion numbers to be used. You do so in the SAP DI in Customizing for Material Requirements Planning under "Define BOM Explosion Control," where you set the BOM Explosion Number indicator. The BOM explosion date cannot be used for assemblies/components that you continue planning in the SAP APO. In this case, the start date of the planned order, which the SAP APO generates for the requirements, determines the explosion date for the iPPE data for assemblies. Start-up parameters from the order for the final product cannot be passed on to components that are indicated as always collective requirements; start-up parameters are not taken into consideration at explosion. Start-up parameters are taken into consideration in planning only for components that you have indicated as individual customer requirement in the product master. EXAMPLE

GO10

DEFINITION See Opening period Opening date The production calendar for the location is a decisive factor in determining the opening date.

planning_time_fence adjustment_horizon

Product-Specific Planning Time Fence in Workdays Adjustment Horizon in Work Days/sapapo/rrp_fixhz /sapapo/ajhoz

dec/ 11/ 0 dec/ 11/ 0

GP8


GQ8


GP9

10

GQ9

10

GP10

DEFINITION Period during which planning is fixed for the product for the following Production Planning and Detailed Scheduling (PP/DS) procurement planning functions and heuristics: Action Cover dependent and stock transport requirements immediately if possible Action Cover dependent and stock transport requirements immediately Heuristics that execute procurement planning and can create or delete procurement proposals These heuristics include, for example, the standard heuristic SAP_PP_002 for planning standard lots. The standard heuristic SAP_PCM_DIS for dissolving production campaigns The PP/DS planning time fence begins at the current time and continues for the given number of workdays into the future. use The system cannot create or delete any receipt elements using the procurement planning functions given above within the PP/DS planning time fence. If the system creates a new receipt for the product, it has to schedule the procurement proposal so that the availability date/time of the receipt is outside the planning time fence. Since existing receipts, whose availability date/time is in the PP/DS horizon, are firmed, the system may, at most, only re-explode the PPM plan, the iPPE process structure or the production data structure (PDS) for these receipts. Note that in the case of a procurement proposal with several output products, the system only takes into account the planning time fence of the product for which the system executes planning; the system does not consider the planning time fences of the other output products. You use the PP/DS planning time fence if you have completed short and medium-term procurement planning for the product and want to prevent changes being made by automatic procurement planning. In the PP/DS planning time fence, you only want to execute sequence optimization on the resources for the existing in-house production orders. You can, however, manually create, change or delete receipts at any time in the PP/DS planning time fence. No PP/DS functions and heuristics, other than the ones mentioned above, consider the PP/DS planning time fence. dependencies The system determines the workdays from the production calendar for the location. If you have not maintained any data in the production calendar, all days are workdays. note You can specify a time fence interactively in the product view. It may override the planning time fence in the following way: If the time fence is after the end of the PP/DS planning time fence, planning is fixed until the time fence. If the time fence is before the end of the PP/DS planning time fence, planning is fixed until the end of the planning time fence.

GQ10

definition use This horizon is relevant to sales order oriented planning. In sales order oriented planning you only convert procurement proposals (planned orders and purchase requisitions) into manufacturing orders or purchase orders if theses procurement proposals are used to cover sales orders. Using specific Production Planning and Detailed Scheduling heuristics, you delete planned independent requirements for which there are no sales orders, and adjust the purchase requisitions and planned orders used to cover these planned independent requirements accordingly. To adjust the planned independent requirements and procurement proposals for selected products, you use the standard heuristic SAP_PP_015. This heuristic executes the adjustment for all procurement proposals that start in the adjustment period. You can define the adjustment period using the adjustment horizon. Using the standard heuristic SAP_PP_016 you execute the adjustment for selected orders. The adjustment horizon and the adjustment period are not relevant here.

req_ascertainment_horizon ppds_horizon procurement_type

Requirements Ascertainment Horizon in Workdays PP/DS Horizon in Calendar Days Procurement Type/sapapo/cthor /sapapo/convh /sapapo/beskz

dec/ 11/ 0 dec/ 3/ 0 char/ 1/

EEEE

EEEE

FFFFF

EEEE

EEE

FFF

GT6

F External Procurement E In-House Production X External Procurement or In-House Production P External Procurement Planning

GR8


GR9

10

GS9

3

GT9

1

GR10

definition use This horizon is relevant to sales order oriented planning. In sales order oriented planning you only convert procurement proposals (planned orders and purchase requisitions) into manufacturing orders or purchase orders if these procurement proposals are used to cover sales orders. Using a specific Production Planning and Detailed Scheduling heuristic (standard heuristic SAP_PP_014 ) you can determine the planned independent requirements for which there are no sales orders. You determine these planned independent requirements for procurement proposals that start in the requirements ascertainment period. You can define the requirements ascertainment period using the requirements ascertainment horizon. You can use the results to ask your customers to issue sales orders.

GS10

DEFINITION USE You specify a location-product-specific PP/DS horizon here. If you do not enter any value for the PP/DS horizon or if you enter the duration '0', the system automatically uses the SNP production horizon as the PP/DS horizon. Therefore, the PP/DS horizon is as long as the SNP production horizon. This means the planning intervals for SNP and PP/DS are sequenced with no gaps or overlaps. If the SNP production horizon also has a duration of 0, the system uses the PP/DS horizon from the planning version. hints You can use the PP/DS firming horizon within the PP/DS horizon to firm (short-term) planning for planning with procurement planning heuristics. Supply Network Planning (SNP) is permitted to plan outside of the SNP production horizon only. If the SNP production horizon is smaller than the PP/DS horizon, the planning horizons of SNP and PP/DS overlap. SNP and PP/DS can both use this overlapping period for planning.

GT10

DEFINITION Defines how the product is procured. The following procurement types are available: F - external procurement E - in-house planning X - external or in-house production P - external procurement planning. If you do not enter anything in the field, the system assumes X. DEPENDENCIES The procurement type is independent of the location type, which means that there can even be in-house production in a distribution center: if a product is packed in a distribution center, it can be given a new product number as a result of having been packed.

EEEE

EE

FFFFFF

EEEEE

EEE

FFFFFF

FFFF

planned_delivery_time external_cost_function

Planned Delivery Time in Days Supply Network Planning: External Cost Function/sapapo/plifz /sapapo/snpcosex

dec/ 3/ 0 char/ 10/

GU9

3

GV9

10

GU10

DEFINITION Number of workdays required to acquire the product or service using external procurement. The system uses the supplier location's production calendar to determine the planned delivery time. If a production calendar is not defined at the supplier location, the system calculates the planned delivery time in calendar days. USE If you have various suppliers for a product, you have to specify an average value. This also applies if you always order the product from the same supplier, but the supplier's delivery times vary. Use in Supply Network Planning (SNP) The planned delivery time is used differently in heuristic-based planning and optimization-based planning: SNP heuristic: The system takes into account the planned delivery time with both types of external procurement; both when the source location is defined in the supply chain model and when it is not known. If you have also defined an SNP stock transfer horizon, the system uses the larger of the two horizons. SNP optimizer: The system only takes into account the planned delivery time if there is no source location for external procurement. Use in Capable-to-Match (CTM) The system only takes into account the planned delivery time if there is no source location for external procurement.

GV10

Use Cost functions are used by optimization-based planning in Supply Network Planning (SNP), to calculate the costs of procuring, producing, and transporting varying quantities of products. The following types of cost function are available: The cost function in the location product master defines the cost of procurement. The cost function in the production process model (PPM) or in the production data structure (PDS) defines the costs of production. The cost function in the master data of the transportation lane defines the transportation costs. Example You specify a quantity interval of 22,000 to 33,000 pieces with a fixed cost of 44,000 and a variable cost of 10. The quantity the SNP optimizer recommends for procurement, production, or transportation is 25,000 pieces. The system calculates the costs as follows: 44,000 + 10 x (25,000 - 22,000) Dependencies You define the cost functions using the Maintain pushbutton.

procurement_costs storage_costs

Procurement Costs for Product Product-Dependent Storage Costs/sapapo/proc_cost /sapapo/scost

dec/ 13/ 3 dec/ 13/ 3

GW9

17

GX9

17

GW10

DEFINITION USE In this field, you can specify costs for procuring a location product that are taken into account in optimization-based planning in Supply Network Planning (SNP). The SNP optimizer uses these costs if you have selected the linear optimization method in the SNP optimizer profile in Customizing for SNP. In addition, the SNP optimizer takes account of the procurement costs when calculating the penalty costs for reusing or disposing of a product whose shelf life date is past (if you have set this in the SNP optimizer profile). DEPENDENCIES If, in the SNP optimizer profile, you have chosen the discrete optimization method (for example, because you want to be able to perform lot size planning), you enter a cost function in the neighboring field. If the validity period of the cost function is exceeded, the SNP optimizer takes account again of the procurement costs specified here. EXAMPLE

GX10

Used in Supply Network Planning and Production Planning and Detailed Scheduling to calculate how much it costs to store the product in the associated storage resource (warehouse) per the base unit of measure and per day.

safty_stock_violation_penalty gr_processing_time gi_processing_time

Penalty Costs for Safety Stock Violation Goods Receipt Processing Time Goods Issue Processing Time/sapapo/sspen /sapapo/grprt /sapapo/giprt

dec/ 13/ 3 dec/ 11/ 0 dec/ 11/ 0

GZ8


HA8


GY9

17

GZ9

10

HA9

10

GZ10

DEFINITION The time between the delivery or the production of a product and its availability as stock. This time is used, for example, as handling time or time for quality control, and is added to the transport duration or production time of a product. Production Planning and Detailed Scheduling To enable the scheduling of the goods receipt for Production Planning and Detailed Scheduling, you must have maintained a handling resource in the master data for the location. Supply Network Planning You can define in Customizing for Supply Network Planning (SNP) under Basic Settings -> Maintain Global SNP Settings, whether the system is to consider the goods receipt processing time when creating SNP planned orders and determining the production process model (PPM) or the production data structure (PDS). The default value is Processing Time, meaning the system considers the goods receipt processing time. To schedule the exact goods receipt processing time, the system uses the calendar of the calendar resource defined in the PPM or in the PDS. When creating deployment stock transfers, the system always considers the goods receipt processing time. A day for goods receipt in SNP is one day with 24 hours. A day in PP/DS corresponds to 24 working hours. This means that if the handling resource is a time stream resource (single/multi-level resource), the resource has to be available 24 hours a day so that the goods receipt is only actually one day. If the availability of the resource is less than 24 hours (for example, due to breaks), one day goods receipt processing time can be spread over several days. Transport duration/production time: 3 days Goods receipt time: 1 day 3 days + 1 day = 4 days -> The product is available on the fifth day.

HA10

DEFINITION The time between issuing the product from storage and transporting it. This time is used as handling time or time for quality control, and is added to the transport duration (Supply Network Planning and PP/DS) of a product. Goods issue time: 1 day Transport duration: 3 days 1 day + 3 days = 4 days -> The product is available on the fifth day.

nd_gr_costs nd_gi_costs

Goods Receipt Costs Network Design Goods Issue Costs in Network Design/sapapo/nd_cost_we /sapapo/nd_cost_wa

dec/ 15/ 2 dec/ 15/ 2

HB9

20

HC9

20

HB10

DEFINITION Defines the unit of measure for a product which can be received or issued. HINTS In Network Design, these costs can be incurred through: external procurement procurement via a transportation lane

HC10

DEFINITION Unit of measure for a product which can be received or issued. Use Costs incurred for goods issue when a product is being transported to another location via a transportation lane.

nd_dlvry_time_quota nd_length_of_storage

External Key for the Delivery Time Quota Profile Network Design: Average Time in Storage in Days/sapapo/dtqky /sapapo/scc_nd_stordu

char/ 20/ dec/ 15/ 2

HD9

20

HE9

20

HD10

DEFINITION Profile key for delivery time quota, maintained in Customizing.

HE10

DEFINITION Determines the average time the location product is kept in storage. USE This enables you to determine the storage costs. The total storage costs are calculated from the product storage costs and the average time in storage. This time is also used to determine the average stock level.

nd_prduction_act_per_week no_order_fix_flag

Average Number of Production Operations per Week Do not fix orders during manual creation/sapapo/nd_mean_prod_per_week /sapapo/snpnofix

dec/ 5/ 2 char/ 1/

HG6

Order fixed when created manually X Order not fixed when created manually

HF9

6

HG9

1

HG10

DEFINITION USE This indicator is only relevant to Supply Network Planning (SNP). If you set this indicator, orders that you created manually in interactive SNP planning are not automatically fixed. A fixed order is an order that cannot be changed or deleted in the next SNP planning run (heuristic, optimization, capable-to-match). DEPENDENCIES EXAMPLE

lot_size_strategy lot_size_start_point

Strategy for Periodic Lot Size Creation in SNP Start Time for Grouping Horizon/sapapo/snplotstrat /sapapo/snplotbeg

char/ 1/ char/ 1/

HH6

Lot is in the first demand period 1 Lot is always in the first period 2 Lot is always in the last period

HI6

Start with the first period X Start with the period where there is a shortage

HH9

1

HI9

1

HH10

DEFINITION USE This indicator is only relevant for heuristic-based planning in Supply Network Planning (SNP). It is used in conjunction with the lot size grouping procedure, which you set using the Period Lot Size indicator. You can specify the period of the grouping horizon in which the combined demand is placed. The following options are available: Blank: The combined demand is placed in the first period of the grouping horizon where demand exists. 1: The combined demand is placed in the first period of the grouping horizon. 2: The combined demand is placed in the last period of the grouping horizon. DEPENDENCIES You set the start of the grouping horizon as well as the period type and the number of periods in this horizon in the Lot size grouping, Period type and No. of Periods fields. EXAMPLE

HI10

DEFINITION USE This indicator is only relevant for heuristic-based planning in Supply Network Planning (SNP). It is used together with the period lot-sizing procedure, which you set using the Period Lot Size indicator. You can specify when you want the system to start grouping the demands together (so, when the grouping horizon starts). The following options are available: Blank: The grouping of demands starts in the first period of the planning buckets profile defined in the planning book (as a rule, today's date). X: The grouping of demands starts in the first period of the planning buckets profile where there is a supply shortage. DEPENDENCIES You use the Period Type and No. of Periods fields to specify the type and number of periods in the grouping horizon. EXAMPLE

product_location_penalty

fixed_pegging_indicator product_id

Retain Fixed Pegging for Product on Document Change Product GUID (Length 32)/sapapo/dm_fixpeg_prod_setting bapi10001matid_32

char/ 1/ char/ 32/

HK4

MEANING Transfer parameter for location-dependent penalty costs. HINTS Note that it is currently possible to work with a planning version during a method call only. If several different planning versions are specified in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority", processing is terminated and an error message is issued. If the data entered in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" is planning-version-independent, the "PlanningVersion" field must be empty or contain the value "000". It is not possible to set planning-version-dependent data for the active planning version only ("000"). The data for the active planning version is always also valid for the other planning versions if specific, planning-version-dependent data has not been maintained for them.

HJ6

Fixed Pegging According to Client Setting 1 Fixed Pegging Is Active for Product 2 Exclude Product from Fixed Pegging

HJ9

1

HK9

32

HJ10

DEFINITION You use this indicator to retain fixed pegging for the product even after a document change (for example, after converting a planned order into a production order). USE DEPENDENCIES You can activate fixed pegging for all products within a client by setting the Fixed Pegging indicator in the global settings. You are able to activate fixed pegging specifically for only particular products. In this case, you set the indicator to 1 in the product master for the products. However, you can also specifically exclude particular products from fixed pegging if you have activated fixed pegging at client level. To do this, set the indicator to 2 for the relevant products. EXAMPLE

HK10


product product_int location_id location

External Product Indicator Product ID Location GUID (Length 32) External Location ID/sapapo/ext_matnr /sapapo/matnr bapi10002locid_32 /sapapo/ext_locno


HL8


HM8


HL9

40

HM9

40

HN9

32

HO9

20

HL10


HM10


HN10


HO10


HL11


HM11


HO11


loctype location_int requirement_type planning_version

Location Type Location Requirements Type Planning Version/sapapo/c_loctype /sapapo/locno /sapapo/snpdemcld /sapapo/vrsioex

char/ 4/ char/ 20/ numc/ 1/ char/ 10/

HP6


HR6

1 Regard as a customer demand 5 Regard as corrected demand forecast 6 Regard as demand forecast

HP9

4

HQ9

20

HR9

1

HS9

10

HP10


HQ10


HR10

DEFINITION The demand priority is used in the demand calculation. WHAT_TO_DO Enter the demand priority defined in the ATP category groups in ATP customizing.

HS10


HQ11


non_delivery_penalty

Penalty for Not Delivering (Costs per Base Unit of Measure)/sapapo/snpndpend

dec/ 13/ 3

HT9

17

HT10

Definition Here you specify penalty costs for not delivering requested product quantities. The SNP optimizer uses these penalty costs within its calculations. Use You can specify the penalties for not delivering customer requirements, the demand forecast, and the corrected demand forecast separately. You have the option here of dividing the demand forecast into two different key figures and giving each one a different weighting. For example, you can give already existing forecasts (demand forecasts) a different weighting to new forecasts (corrected demand forecast). You can also specify time-dependent penalty costs and, thus, assign a time priority to requirements. To do this select the corresponding pushbutton with the Create Time-Dependent Penalty Costs quick info and enter a penalty cost validity end date. Dependencies The system uses the base unit of measure defined in the product master to calculate this penalty. It considers customer requirements as priority 1, the corrected demand forecast as priority 2, and the demand forecast as priority 3. The SNP optimizer first calculates the penalty costs on a location-dependent basis, then on a non-location-dependent basis.

delayed_delivery_penalty max_delay

Delay Penalty (Costs per Day and Base Unit of Measure) Maximum Allowed Delay (in Days)/sapapo/snplapend /sapapo/snpmaxlad

dec/ 13/ 3 dec/ 3/ 0

HU9

17

HV9

3

HU10

Definition Gives the penalty cost rate per day that is used by the SNP Optimizer to weight the delayed delivery of a product with regard to the planned delivery date. The penalty for delayed delivery of the requirement quantities is measured per base unit of quantity. Use You can set separately the delay penalties for customer requirements, the requirement forecast and the corrected requirements forecast. You thus have the opportunity to divide the requirements forecast into two different indicators and to weight these differently. You can, for example, weight those forecasts already available (requirements forecast) differently to new forecasts (corrected requirements forecast). You can also define time-dependent penalty costs and, therefore, assign a time priority to requirment. To do this, select the corresponding pushbutton with quick info text Create Time-Dependent Penalty Costs. Dependencies To calculate this penalty the system uses the base unit of quantity defined in the product master. Customer requirements are viewed as Priority 1 by the system, the corrected requirement forecast as priority 3 and the requirement forecast as priority 3.

HV10

Indicates the maximum number of days a product can be late. After the maximum late date has passed, the system stops calculating late penalties and determines the non-delivery penalties. You can also define the maximum number of days a product can be late as time-dependent. To do this, select the corresponding pushbutton with quick info text Create Time Dependent Penalty Costs.

product_location_priority

date_valid_to product_id product

Time stamp at end of validity period Product GUID (Length 32) External Product Indicator/sapapo/scc_valtotstmp bapi10001matid_32 /sapapo/ext_matnr

dec/ 15/ 0 char/ 32/ char/ 40/

HX4

MEANING Transfer parameters for priorities of location products. HINTS Note that it is currently possible to work with a planning version during a method call only. If several different planning versions are specified in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority", processing is terminated and an error message is issued. If the data entered in the parameters "ProductLocationVersion", "ProductLocationPenalty", and "ProductLocationPriority" is planning-version-independent, the "PlanningVersion" field must be empty or contain the value "000". It is not possible to set planning-version-dependent data for the active planning version only ("000"). The data for the active planning version is always also valid for the other planning versions if specific, planning-version-dependent data has not been maintained for them.

HY8


HW9

19

HX9

32

HY9

40

HX10


HY10


HY11


product_int location_id location loctype location_int

Product ID Location GUID (Length 32) External Location ID Location Type Location/sapapo/matnr bapi10002locid_32 /sapapo/ext_locno /sapapo/c_loctype /sapapo/locno

char/ 40/ char/ 32/ char/ 20/ char/ 4/ char/ 20/

IC6


HZ8


HZ9

40

IA9

32

IB9

20

IC9

4

ID9

20

HZ10


IA10


IB10


IC10


ID10


HZ11


IB11


ID11


product_model

validity_end_date planning_version priority ranking product_id

Validity period end Planning Version Product Priority Rank of Product Product GUID (Length 32)/sapapo/datet /sapapo/vrsioex /sapapo/prio /sapapo/mrank bapi10001matid_32

dec/ 15/ 0 char/ 10/ int1/ 3/ int4/ 10/ char/ 32/

45CF3ED23D966AE4E100045CF3EDF3D966AE4E100045CF3EEC3D966AE4E100045CF3EF93D966AE4E1000

45D154B252AE40C6E100045D154B652AE40C6E100045D154BA52AE40C6E100045D154BE52AE40C6E1000

45D154C652AE40C6E100045D154C252AE40C6E100045D154CA52AE40C6E100045D154CE52AE40C6E100045D420CB20B9288FE1000

45CF40DC3D31680AE100045CF40E93D31680AE100045CF40F63D31680AE100045CF41033D31680AE1000

45D5265026066BDEE100045D5265426066BDEE100045D5265826066BDEE1000

45D55BB058E235F4E100045D55BA858E235F4E100045D55BAC58E235F4E1000

II4

MEANING Transfer parameter for model assignments. RANGE If a model assignment was not made for a product when the product was created, the product is automatically added to the active model. If you do not want this automatic assignment to take place, you have to set the "NoAutoAssignmentFlag" indicator in the "SaveOptions" parameter. However, if model assignments are made for the product, the product is only assigned to the models specified. Automatic model assignment does not take place when models are changed. Only the specified model assignments are executed. If the "RemoveFlag" indicator is set, the product specified is removed from the model. For this, there is a check whether the product is still being used in the model entered. If the product is still being used, the removal is rejected and an error message is returned. DEFAULT

IE9

19

IF9

10

IG9

3

IH9

5

II9

32

IF10


IG10

Use The system can derive the priority of the order from the priority of the product. You can assign values from 0 to 255 for the priority. The value 1 represents the highest priority, whereas 255 is the lowest priority you can enter. If you enter the value 0 or no value, the system equates this with priority 256. You can maintain the priority on the SNP2 tab page only. The priority field on the PP/DS tab page is display only. Use in PP/DS In production planning and detailed scheduling(PP/DS), the order priority can be derived from the product priority or the sales order. On the basis of the order priority, you can make a planning decision, for example, or carry out a sequence planning using a detailed scheduling heuristic. You specify which priority the system uses in PP/DS in the planning version (PP/DS: Determination of Order Priorities field). Use in CTM Capable-to-Match Planning (CTM) takes into account the value for the prioritization in requirement prioritization. For this purpose, you must specify on the Requirements tab page in the Capable-to-Match profile that the requirements are to be prioritized according to the criterion MATPRIO. However, the value specified here is not taken into account if you have entered a value for priority and/or rank in the location product master record under time-dependent priority. Use in SNP In Supply Network Planning(SNP), the product priority is only used in the area of capacity leveling. This field is not taken into account in the SNP heuristic, the SNP optimizer, deployment, or the Transport Load Builder (TLB). For capacity leveling, you can specify in the Order Prioritization (or Priority ) field that the product priority is to be taken into account. The system then moves orders for products with the highest priority first to earlier periods or orders for products with the lowest priority first to later periods, depending on the system setting.

II10


45D9555D5313057DE100045D955615313057DE1000045D955655313057DE1000045D955695313057DE10000

45D9556D5313057DE100045D955715313057DE10000

45D955755313057DE1000045D955795313057DE1000045D955815313057DE1000045D955855313057DE1000045D955895313057DE1000045D9558D5313057DE1000

45D9747C71A73EA3E100045D9748071A73EA3E100045D9748471A73EA3E100045D9748871A73EA3E100045FF7334728E090AE10000

45D9748C71A73EA3E100045D9749071A73EA3E100045D9749471A73EA3E1000

45D9749871A73EA3E100045D9749C71A73EA3E100045D974A071A73EA3E100045D974A471A73EA3E100045D974A871A73EA3E100045D974AC71A73EA3E1000

45CF3EDF3D966AE4E100045CF3ED23D966AE4E100045CF3EEC3D966AE4E100045CF3EF93D966AE4E1000

product product_int location_id

External Product Indicator Product ID Location GUID (Length 32)/sapapo/ext_matnr /sapapo/matnr bapi10002locid_32


AC00230 AC00230 45AEF358F2ED55BEE10000AC00039 AC00039 45AEF358F2ED55BEE10000AC00146 AC00146 45AEF358F2ED55BEE10000AC00157 AC00157 45AEF358F2ED55BEE10000

010681 0000000000000000000000000000000000010681 45AEF358F2ED55BEE100008000 0000000000000000000000000000000000008000 45AEF358F2ED55BEE10000010680 0000000000000000000000000000000000010680 45AEF358F2ED55BEE100008001 0000000000000000000000000000000000008001 45AEF358F2ED55BEE10000

A00904 A00904 45AEF358F2ED55BEE10000A80004 A80004 45AEF358F2ED55BEE10000A70000 A70000 45AEF358F2ED55BEE10000A50005 A50005 45AEF358F2ED55BEE10000A70001 A70001 45AEF358F2ED55BEE10000

AM00110 AM00110 45AEF358F2ED55BEE10000AM00060 AM00060 45AEF358F2ED55BEE10000AM00080 AM00080 45AEF358F2ED55BEE10000AM00090 AM00090 45AEF358F2ED55BEE10000

10690 0000000000000000000000000000000000010690 45AEF358F2ED55BEE1000010691 0000000000000000000000000000000000010691 45AEF358F2ED55BEE1000010688 0000000000000000000000000000000000010688 45AEF358F2ED55BEE10000

A74000 A74000 45AEF358F2ED55BEE10000A74002 A74002 45AEF358F2ED55BEE10000A74003 A74003 45AEF358F2ED55BEE10000

IJ8


IK8


IJ9

40

IK9

40

IL9

32

IJ10


IK10


IL10


IJ11


IK11


903106 0000000000000000000000000000000000903106 45AEFDAEFD790E82E1000901216 0000000000000000000000000000000000901216 45AEFDAEFD790E82E1000900097 0000000000000000000000000000000000900097 45AEFDAEFD790E82E1000903107 0000000000000000000000000000000000903107 45AEFDAEFD790E82E1000

9000 0000000000000000000000000000000000009000 45AEFDAEFD790E82E10009103 0000000000000000000000000000000000009103 45AEFDAEFD790E82E1000

RMP0003 RMP0003 45AEFDAEFD790E82E1000RMP0043 RMP0043 45AEFDAEFD790E82E1000CTC3180 CTC3180 45AEFDAEFD790E82E1000CTC3181 CTC3181 45AEFDAEFD790E82E1000CTC3189 CTC3189 45AEFDAEFD790E82E1000CTC3179 CTC3179 45AEFDAEFD790E82E1000

200340 0000000000000000000000000000000000200340 45AEFD93FD790E82E10000200380 0000000000000000000000000000000000200380 45AEFD93FD790E82E10000201114 0000000000000000000000000000000000201114 45AEFD93FD790E82E10000200809 0000000000000000000000000000000000200809 45AEFD93FD790E82E100000000000000000000000000 BSGSLDE1 45AEFD93FD790E82E10000

4013 0000000000000000000000000000000000004013 45AEFD93FD790E82E100004014 0000000000000000000000000000000000004014 45AEFD93FD790E82E100004008 0000000000000000000000000000000000004008 45AEFD93FD790E82E10000

10311 0000000000000000000000000000000000010311 45AEFD93FD790E82E1000010307 0000000000000000000000000000000000010307 45AEFD93FD790E82E1000013248 0000000000000000000000000000000000013248 45AEFD93FD790E82E1000013247 0000000000000000000000000000000000013247 45AEFD93FD790E82E1000013241 0000000000000000000000000000000000013241 45AEFD93FD790E82E1000013240 0000000000000000000000000000000000013240 45AEFD93FD790E82E10000

AC00039 AC00039 45AEF15FF0D64280E10000AC00230 AC00230 45AEF15FF0D64280E10000AC00146 AC00146 45AEF15FF0D64280E10000AC00157 AC00157 45AEF15FF0D64280E10000

location loctype location_int model

External Location ID Location Type Location Model Name in Supply Chain Network/sapapo/ext_locno /sapapo/c_loctype /sapapo/locno /sapapo/c_modelid


M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000

M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000

M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000

M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000

M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000

M026 1001 M026 000M026 1001 M026 000M026 1001 M026 000

IN6


IP8


IM9

20

IN9

4

IO9

20

IP9

22

IM10


IN10


IO10


IP10


IM11


IO11


M028 1001 M028 000M028 1001 M028 000M028 1001 M028 000M028 1001 M028 000

M028 1001 M028 000M028 1001 M028 000

M028 1001 M028 000M028 1001 M028 000M028 1001 M028 000M028 1001 M028 000M028 1001 M028 000M028 1001 M028 000

M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000

M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000

M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000M027 1001 M027 000

L044 1002 L044 000L044 1002 L044 000L044 1002 L044 000L044 1002 L044 000

remove_flag

Select an Option (Yes = 'X', No = ' ')bapiyesno

char/ 1/

IQ6

No X Yes

IQ9

1

logical_system

logical_system


-> documentation

char/ 10/

A1

bapi_rssrvaps_savemulti_30a

B1

bapi_rssrvaps_getlist

A2

FUNCTIONALITY With this method you can create or change version-independent resources. If the resource specified does not yet exist for the specified business system group, it is created. If the resource already exists, it is changed according to the transferred data. HINTS Note that this method executes an internal COMMIT WORK and therefore external commit control is not possible. The "ChangeMultiple" method must be used to change version-dependent resources. Changes to the version-independent resource made using this method are not automatically also carried out on the corresponding version-dependent resources. When this method is executed, no database locks are set and evaluated, since the interface has highest priority. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information

B2

FUNCTIONALITY This method can be used to read resources for specified selection criteria. HINTS You have the following options for selecting resources. Combinations between the alternatives are not possible, or are ignored. Selection by specifying resource GUIDs: "ResourceGuids" Selection using RANGES tables: "ResourceSelection" + "LocationSelection" (optional) + "LoctypeSelection" (optional) + "RestypeSelection" (optional) Selection by specifying the external key: "ResourceKeys" Selection by specifying the internal key: "ResourceIntKeys" Selection by specifying the GUID of the assigned maintenance order: "ResourceOrdids" You can limit selection options 1, 2, 3, and 4 using the following selections: "PlanningVersion" "PlannerSelection" "IsBottleNeck" "FinitePlanning" "WithDeletedRes" For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General Information

B4


B8


B9

10

B10


resource_head

resuid resource restype location

Resources GUID (Length 32) External Name of Resource Resource Category External Location IDbapi10004resid_32 bapi10004ext_resname /sapapo/cres_restype /sapapo/ext_locno


C4

MEANING Transfer parameters for general data for resources. RANGE Key fields: "Resource" or "Resuid" HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

E6

P Production T Transportation S Storage Location H Handling Unit

C9

32

D9

40

E9

1

F9

20

C10


D10

DEFINITION Indicates the resource name.

E10

DEFINITION The resource category describes the usage of the resource, for example as a production resource. use The resource category is a purely descriptive characteristic that you can use for selecting resources for resource maintenance, for example. The resource category is not linked with a planning functionality.

F10


D11

BAPI10004RESOURCEHELP/RESOURCE_EXT

F11


loctype calendar type

Location Type Factory Calendar ID Resource Type/sapapo/c_loctype /sapapo/cres_calendar /sapapo/cres_resource_type

char/ 4/ char/ 2/ numc/ 2/

G6


I6

01 Multiactivity Resource 02 Single-Activity Resource 03 Bucket Resource 04 Single Mixed Resource 05 Multimixed Resource 06 Line Resource 07 Line Mixed Resource 08 Transportation Resource 09 Vehicle Resource 10 Calendar Resource 11 Calendar Mixed Resource

H8

Valuetable: TFACD

G9

4

H9

2

I9

2

G10


H10

DEFINITION The factory calendar defines workdays and non-workdays. Hinweis You can define workdays and non-workdays flexibly in the time intervals for the capacity variants.

I10

DEFINITION Indicates the resource type: 0: Single activity resource 1: Multiactivity resource 3: Bucket resource

dimension dimension_bucket

Dimension of the Resource (Continuous) Dimension of the Resource (Bucket View)/sapapo/cres_dimid /sapapo/cres_dimid_bucket

char/ 6/ char/ 6/

J8

Valuetable: T006D

K8

Valuetable: T006D

J9

6

K9

6

J10

DEFINITION Specifies in which dimension (for example, weight, volume) the resource is scheduled. The dimension can only be changed in the model-independent resource.

K10

DEFINITION Describes in which dimension (for example, weight, volume) a resource is scheduled. The dimension can only be changed in the model-independent resource.

begti endti breaktime

Start Time for the Working Day Time When Working Day Ends Break Duration/sapapo/cres_begti_disp /sapapo/cres_endti_disp /sapapo/cres_break_disp

tims/ 6/ tims/ 6/ tims/ 6/

L9

8

M9

8

N9

8

buffertime buffertime_unit buffertime_unit_iso

Resource-Dependent Time Buffer Unit of Measure for Time Buffer ISO code for unit of measurement/sapapo/cres_buffertime_disp /sapapo/cres_buffertime_unit /sapapo/isocd_unit

numc/ 3/ unit/ 3/ char/ 3/

P8


Q8

Valuetable: T006I

O9

3

P9

3

Q9

3

O10

DEFINITION In this field you define the duration of the time buffer of the resource. You use the time buffer in Production Planning and Detailed Scheduling as a safety time, in order to protect the resource or the activities, which are processed on the resource, from unforeseen delays in material staging. dependencies You define in the production process model in the reference subtype field if the system can use the time buffer for a time relationship between two activities. You define if the system can use the time buffer for scheduling in the detailed scheduling strategy or in the optimization profile. EXAMPLE There is an end-start relationship with a minimum interval of one hour between two activities A10 and A20. A10 is processed on the resource R1, and A20 on the resource R2. If you have entered a time buffer of an hour in resource R2, A10 must be completed on R1 at latest two hours before the start of A20 on R2.

noindivres noindivres_unit

Capacity of Resource Unit of Measure for the Capacity of a Multiactivity Resource/sapapo/cres_noindivres /sapapo/cres_noindivres_unit


R8

Reference Table: /SAPAPO/RES_HEAD Reference Field: NOINDIVRES_UNIT

S8


R9

17

S9

3

R10

DEFINITION Defines the capacity of the multi-activity resource. The capacity is relevant for multi-activity resources. Only the productive time is relevant for single activity resources; these resources have capacity 1 without a unit of measurement. example A saw can cut a maximum of four meter long rods into slices. It can also take several rods that added together have a maximum length of four meters. The capacity of the saw is thus four meters. dependencies If required, enter the unit of measure for the capacity. If you want to describe the capacity of the resource using a particular number of individual resources, do not enter a unit of measure.

S10

DEFINITION Defines the unit of measurement for the capacity of a multi-activity resource. use If you would like to describe the capacity of the resource by a particular number of individual resources (for example, several individual machines), do not enter a unit of measurement. Hints In the case of single activity resources, the capacity and their unit of measure is not relevant. Only the productive time is relevant for these resources.

noindivres_unit_iso indivres_cap

ISO code for unit of measurement Size of the Transportation Resource/sapapo/isocd_unit /sapapo/cres_indivres_cap

char/ 3/ quan/ 13/ 3

T8

Valuetable: T006I

U8

Reference Table: /SAPAPO/RES_HEAD Reference Field: NOINDIVRES_UNIT

T9

3

U9

17

U10

DEFINITION The size of a transportation resource indicates, for example, how large the volume of an individual transportation is. The total bucket capacity is then made up of the individual transportation resources (bucket capacity divided by size).

utilization define_buckets

Percentage Rate of Resource Utilization Definition of Bucket Capacity for Mixed Resource/sapapo/cres_utilization /sapapo/cres_define_buckets

dec/ 6/ 3 char/ 1/

V6

10.000 Value Range for Rate of Resource Utilization

W6

From Continuous Capacity X Maintain

V9

7

W9

1

V10

DEFINITION Percentage ratio of the actual available time (productive time) to the theoretically available working time for a resource. use The theoretically available working time (working time minus break times) can be reduced by organizational or technical disturbances, for example machine down time. With the utilization rate you estimate the average reduction. The system calculates the productive time of a resource using the utilization rate and the working time data.

capacity_a capacity_a_unit

Capacity of the Bucket Resource Unit of Measure for the Capacity of a Bucket Resource/sapapo/cres_capacityv1_disp /sapapo/cres_capacityv_unit


X8

Reference Table: /SAPAPO/RES_HEAD Reference Field: CAPACITY_A_UNIT

Y8


X9

17

Y9

3

X10

use You can alternatively: Refer to a particular number of workdays for the capacity, thereby describing, for example, the production rate or usage rate of the resource Create the capacity without reference to time, thereby describing , for example, the transport or storage capacity of the resource dependencies When you want the quantity to apply to a particular number of workdays: Choose using period type the period type day Enter in number of periods the number of days If you want to enter the capacity without a time reference, choose using period type the period type no reference to period.

capacity_a_unit_iso num_of_periods

ISO code for unit of measurement Number of Periods to which the Capacity Applies/sapapo/isocd_unit /sapapo/cres_num_of_periods

char/ 3/ numc/ 3/

Z8

Valuetable: T006I

Z9

3

AA9

3

AA10

definition Number of days to which you apply the capacity. definition By applying the capacity to a time period, you describe, for example, the production rate or usage rate of the resource. dependencies For rates, you choose under Period type the period type Day .

period planner version_active

Period Type Resource Planner Group Active Available Capacity Variant/sapapo/cres_period /sapapo/cres_planner /sapapo/cres_version_active

numc/ 2/ char/ 3/ numc/ 2/

AB6

01 No Period Reference 02 Day

AD8

Valuetable: /SAPAPO/RESVERS

AB9

2

AC9

3

AD9

2

AB10

DEFINITION Determines whether the capacity: Apply to a time period (bucket), thereby describing, for example, a production rate or usage rate Do not apply to a time period, thereby describing a transport or storage capacity use If you do not want to apply the capacity to a time period, choose the period type No period type. If you want to apply the capacity to a time period, choose the period type Day and enter the number of days in Number of periods .

AC10

DEFINITION A planning group is responsible for specific resources.

AD10

DEFINITION Defines the active variant of capacity for the resource. dependencies If you do not define an active variant, the capacity of the resource is either defined by the capacity of the reference resource or, if you have not entered a reference resource, by the standard capacity, which is defined in the resource header.

finite_planning is_bottleneck

Consider Resource Capacity Load The Resource is a Bottleneck Resource/sapapo/cres_lvlind /sapapo/cdps_bottleneck

char/ 1/ char/ 1/

AE6

X Yes No

AF6

X Yes No

AE9

1

AF9

1

AE10

DEFINITION Specifies that the existing capacity load on the resource is taken into account during scheduling.

AF10

DEFINITION Specifies that the resource is a bottleneck resource. use In the detailed scheduling planning board, bottleneck resources can be displayed differently to non-bottleneck resources. In the Production Planning and Detailed Scheduling optimization, you can carry out a campaign optimization for bottleneck resources.

min_gaps overload

Reduce Gaps Maximum Capacity Overload of Resource/sapapo/cdps_minimize_gaps /sapapo/cres_overload

char/ 1/ numc/ 3/

AG6


AG9

1

AH9

3

AG10

definition Specifies that after a planning operation the gaps in the schedule for the resource are reduced, for example after you have deallocated an operation. The operations are shifted as far as possible from the future towards today's date. The sequence of operations remains the same. dependencies This indicator is only relevant to production planning and detailled scheduling.

AH10

DEFINITION Defines by how much (in percent) the resource load may exceed the capacity of the resource, without the system interpreting this situation as a resource overload and triggering Alerts. USE You use this field to control whether an Alert is triggered for a resource overload. dependencies In the Alert profile for PP/DS, you specify whether or not the system is to trigger an Alert for a resource overload.

underload overlap_buckets

Minimum Capacity Load for the Resource Activities can Overlap into Another Period/sapapo/cres_underload /sapapo/cres_overlap_buckets

numc/ 3/ char/ 1/

AJ6


AI9

3

AJ9

1

AI10

DEFINITION The value defined here represents the minimum load (in percentage) defined for the resource capacity. A load below this percentage represents an underload situation.

AJ10

DEFINITION Specifies that an activity may start in one period and end in another (not necessarily in the next period). use As standard, a period is one day. DEPENDENCIES If you do not set this indicator and activitites exist in SNP that last longer then the bucket (day), the system cannot schedule these activities.

start_on_grid min_overlap

Activities can Only Begin at the Start of the Bucket Maximum Overlap of Activities/sapapo/cres_start_on_grid /sapapo/cres_min_overlap

char/ 1/ numc/ 3/

AK6


AK9

1

AL9

3

AL10

use Operations can overlap at a resource leading to a resource overload. In this field, you enter how long a resource overload may exist before the system interprets this as a resource overload and triggers an Alert. dependencies In the Alert profile for PP/DS, you specify whether or not the system is to trigger an Alert for a resource overload.

min_overlap_unit min_overlap_unit_iso

Unit of Measure for the Maximum Overlap of Two Activities ISO code for unit of measurement/sapapo/cres_min_overlap_unit /sapapo/isocd_unit

unit/ 3/ char/ 3/

AM8


AN8

Valuetable: T006I

AM9

3

AN9

3

loss_factor ref_proctime

Percentage Loss Factor when Deriving Bucket Capacity Processing Duration for Reference Operation/sapapo/cres_loss_factor /sapapo/cres_ref_proctime_disp

numc/ 3/ numc/ 3/

AO6

000 Value Range for Loss Factor

AO9

3

AP9

3

AO10

DEFINITION Indicates the reduction in the capacity of the bucket resource for single-mix resources and multi-mix resources. USE Single-activity resources and multi-activity resources can be planned to the very second. They are used to allocate capacity via activities such as setup and tear-down. In order to achieve the same allocation in single or multi-activity resources and bucket resources, you can adjust capacities using the loss factor.

ref_proctime_unit ref_proctime_unit_iso

Unit of Measurement for Processing Duration for Ref. Op. ISO code for unit of measurement/sapapo/cres_ref_proctime_unit /sapapo/isocd_unit

unit/ 3/ char/ 3/

AQ8


AR8

Valuetable: T006I

AQ9

3

AR9

3

timezone takts base_rate_quantity base_rate_quantity_unit

Time Zone Number of Takts Number of Units for the Base Rate Unit of Ratetimezone /sapapo/num_takts /sapapo/base_rate /sapapo/rate_qunit

char/ 6/ numc/ 6/ quan/ 13/ 3 unit/ 3/

AS8

Valuetable: TTZZ

AU8

Reference Table: /SAPAPO/RES_HEAD Reference Field: BR_QUNIT

AV8


AS9

6

AT9

6

AU9

17

AV9

3

AS10

DEFINITION The time zone describes the location of an object relative to its local time. The rule describes the time difference of the time zone in hours/minutes relative to UTC and the begin and end of Summer time. It is neither neccessary nor advisable to use different time zones for Summer and Winter time. Local times can be converted between local time and a UTC time stamp using the ABAP command convert. The parameters are local time (date and time), time zone and UTC time stamp.

AT10

DEFINITION States the number of takts for the affected object in the line structure, which can be a line segment, a line or a line network. A takt is, in a way, a processing station in the production line. A product passes through the line takts and remains in each takt for the duration of the takt time, in order to be processed there. The takt time is the reciprocal value of the rate. If you produce at a rate of 6 pieces per hour, the takt time is 10 minutes. A product can then be processed in each takt for 10 minutes. USE You can only enter the number of takts in the resource as long as the resource has not be assigned to a production line in the PPE line design. As soon as you have assigned the resource, you can enter the number of takts in the line structure. There you can subdivide a production line into line segments over any number of hierarchy levels and then arrange the line segments in each hierarchy level in a network. You define the number of takts in the lowest hierarchy level for the line segment. In the higher hierarchy levels, the system displays the cumulated number of takts. The system does not add up all the takts in the line segments, but calculates the longest (critical) path through the line segment network. The number of takts is, in addition to the takt time, a takt-based scheduling parameter.

AU10

DEFINITION States the number of products that can be produced in the base rate on the production line. The base rate is a rate that is independent of time and consists of a number of measurement units, the measurement unit, the number of time units and the time unit. USE You can enter the standard load of your production line as the base rate. Using this rate, you can schedule in times where the load is normal. If you want to produce at another rate when you have a higher or lower operation rate, you can define a production rate that is dependent on time. Dependencies Using the indicator rate-independent takt you can determine whether the system uses the base rate or the production rate for takt-based scheduling.

AV10

DEFINITION States the unit of measurement for the number of the base rate or the production rate. Dependencies You must be able to convert all products into this unit of measurement.

base_rate_quantity_unit_iso base_rate_time base_rate_time_unit

ISO code for unit of measurement Number of Time Units for a Rate Time Unit of Rate/sapapo/isocd_unit /sapapo/rate_time /sapapo/rate_tunit

char/ 3/ quan/ 5/ 2 unit/ 3/

AW8

Valuetable: T006I

AX8

Reference Table: /SAPAPO/RES_HEAD Reference Field: BR_TUNIT

AY8


AW9

3

AX9

6

AY9

3

AX10

DEFINITION States the number of time units for the base rate or the production rate. USE Using the number of time units, it is possible for you to set the rate at 2 hours, for example.

AY10

DEFINITION States the time unit for the base rate or the production rate. Dependencies

base_rate_time_unit_iso ritt_flg

ISO code for unit of measurement Rate-Independent Takt Time/sapapo/isocd_unit /sapapo/ritt_flg

char/ 3/ char/ 1/

AZ8

Valuetable: T006I

AZ9

3

BA9

1

BA10

DEFINITION Determines how the system adopts the base rate and the production rate for rate-based scheduling. USE When you select the indicator, the system takes the base rate as a basis for rate-based scheduling. The base rate then determines how long a product stays in a takt in order to be processed. The base rate is not dependent on time and therefore the speed of your production line is always constant. The production rate determines which quantities per time unit are produced in a particular time period. By doing so, the production rate determines at which time intervals a product must enter or leave the production line in order to ensure the line meets the required quantity performance. If you do not select the indicator, the system does not use the base rate for rate-based scheduling. The production rate then determines the time for which a product remains in a production line takt and the time at which a product enters and leaves the production line. By doing so, the speed of the production line is determined by the time-dependent production rate.

mdrmodel

Defintion Name for the Product-Dependent Rate/sapapo/cres_mdr_name

char/ 40/

BB9

40

BB10

LS> Explicitly identifies a model for the product-dependent rates. You can enter the product-dependent rates for several products within a model. USE You enter product-dependent rates for the products that you do not want to produce in the base rate or in the production rate. Due to the fact that the base rate is independent of time, you enter the product-dependent rate as a factor in relation to the base rate. You can, for example, enter the factor 0.8 for a product. By doing so, you specify that for this product you can only produce 80% of the amount in the same time compared to other products. The system saves the factor for this product. If you schedule using the production rate, the system multiplies the production rate with the product-dependent factor for the affected product. Before defining the product-dependent rates, you can enter a resource in the production line resource field. The system gives the base rate of the production line resource as a default. You can overwrite this default and the system then calculates the factor automatically. Dependencies After you have defined the model for the product-dependent rates, you can allocate it to the production line resource in the header data on the tab page standard capacity

sort

Freely Selectable Character Sequence for Sorting Resources/sapapo/cres_sort

char/ 30/

BC9

30

BC10

DEFINITION Enables you to sort Resources in planning.

sync_start

Synchronization of Activities when Overlapping Occurs/sapapo/cres_sync_start

numc/ 1/

BD6

0 No Synchronization 2 Synchronization

BD9

1

BD10

DEFINITION Defines whether the system synchronizes the start times of activities on multi-mix resources and multi-activity resources when these activities have the same duration and a further identical characteristic. USE When synchronizing, the system schedules the new activity either at the same start time as an activity with the same duration and characteristic (which has already been scheduled) or, without overlap, before or afterwards. By synchronizing, you can create blocks of activities at the multi-resources that can be processed simultaneously because they have the same duration and characteristic. You specify the value of the characteristic by using a setup group or a setup key that you assign to the operation in the production process model. If the desired start or finish time of an activity falls between the start and finish time of an activity that has already been scheduled with the same characteristic and duration (that is, an overlap has occurred) the system schedules the activity on the same start time as the activity already scheduled, if there is sufficient capacity. If there is not enough capacity at this time, the system schedules the activity before the scheduled activity (scheduling direction backwards) or after the scheduled activity (scheduling direction forwards) without overlap. The system always schedules activities with different durations and characteristics without overlaps. If you select No synchronization, the system schedules activities on multi-resources with overlaps. The system only executes synchronization for multi-resources that you only use as primary resources in the modes of production process models. EXAMPLE Synchronization can be used to model the loading of an oven. Because the oven can only be loaded or unloaded all at once, you must ensure that it is filled to full capacity with products that require the same temperature and duration. Therefore you can only schedule activities for the oven that have the same durations and require the same temperature. Tempering activities with a different duration or temperature can only be loaded into the oven without overlap either before or afterwards. You can model different temperatures using different setup keys that you assign to the operations, and hence to the activities of the operation. hints Note that the setup key and setup group are used differently for multi-resources than for single resources: For single resources, the setup key or setup group classifies the setup status of a primary resource that is required for processing an operation. The setup status of a resource is evaluated by the system during the setup time adjustment or in setup time optimization based on the setup matrix. For multi-resources, the setup key or setup group represents a characteristic of an operation that you wish to use for the synchronization of activities on a primary resource (for example, a certain temperature). DEPENDENCIES Under certain circumstances the synchronization may be violated during planning, for example when changes are made in parallel modes. You can be informed of this situation, and of the start and end date of the affected time period in which activities are not synchronized, in the Alert Monitor by means of a dynamic alert. To activate this option you must select the alert Activity Violates Synchronization for the Resource in the alert profile, on the PP/DS tab page, under Alerts for Activities of a Resource.

sync_compatible matrix_name

Synchronization of Activities when Overlapping Occurs Name of Setup Matrix/sapapo/cres_sync_compatible /sapapo/cdps_matrix_name

numc/ 1/ char/ 20/

BE6

0 No Synchronization 2 Overlap => Same Setup Key

BE9

1

BF9

20

BE10

DEFINITION Applies to multi-activity and multi-mix resources upon which several activities can overlap. The Online Scheduler is used to influence the scheduling of activities on resources. USE Blocks of "related" activities can be mapped to the resources using synchronization. You can choose from the following start relationships: No synchronization. Overlap -> same setup key: If two activities overlap, they have the same setup key. DEPENDENCIES You can only maintain overlaps due the same setup key if synchronized start times were maintained. For multi-activity-resources, you use the setup key to classify activities that may overlap. EXAMPLE Loading an oven is an example for synchronization due to the same setup key: You can use the setup key to identify different temperatures. If you use synchronization, only products that need the same temperature are processed at the same time.

BF10

DEFINITION Name of the setup matrix

ref_resource traty

External Name of Reference Resource Means of Transportbapi10004ext_refresname /sapapo/crestraty

char/ 40/ char/ 10/

BG9

40

BH9

10

BH10

DEFINITION The vehicle is the means by which the transportation between locations is executed. For example: Truck, ship, aircraft The transportation between two locations is specified by allocating vehicles to the lane and by describing them using attributes that are relevant for the transportation; for example, duration and cost of transportation.

days_minus

Validity Period of Available Capacity (In Past)/sapapo/cres_gen_lc_backwards

numc/ 4/

BI9

4

BI10

DEFINITION Defines the start of the validity period of the available capacity of the resource. USE Starting from the day on which the resource is created (or the planning relevant resource data is changed and saved), the system counts the given number of days into the past. You should define the time period relevant for scheduling a resource to be as short as the planning considerations allow. By doing so, you avoid using too much memory in SAP liveCache. hints To update the validity period of a resource without saving the resource again, you can use the report /SAPAPO/CRES_CAPACITY_LENGTHEN . We recommend that you schedule the report periodically.

days_plus storage_capable

Vailidity Period of Res. Capacity (from Today into Future) Resource has Storage Characteristics/sapapo/cres_gen_lc_forward /sapapo/cres_storage_capable

numc/ 4/ char/ 1/

BK6


BJ9

4

BK9

1

BJ10

DEFINITION Defines the end of the validity period of the available capacity of the resource. USE Starting from the day on which the resource was created (or the planning-relevant data for the resource was changed and saved), the system counts the specified number of days into the future. You should define the time period relevant for scheduling a resource to only be as long as the planning considerations require. By doing so, you avoid using too much memory in SAP liveCache. hints To update the validity period of a resource without saving the resource again, you can use the report /SAPAPO/CRES_CAPACITY_LENGTHEN . We recommend that you schedule the report periodically.

BK10

DEFINITION Indicator that assigns not only production capacity but also storage capacity to a resource. When the indicator is set, the resource can contain products.

min_storage max_storage

Minimum Production Quantity Maximum Stock Level/sapapo/cres_min_storage /sapapo/cres_max_storage

quan/ 15/ 3 quan/ 15/ 3

BL8

Reference Table: /SAPAPO/CRES_STORAGE Reference Field: STORAGE_UNIT

BM8


BL9

20

BM9

20

BL10

DEFINITION The minimum quantity that has to be filled into the resource in order for the resource to be used for production. EXAMPLE You want to produce something in a mixing tank. If one or more synchronized activities are used for production at this resource, the minimum production quantity must be in the tank. This is important, for example, in the case of resources with a mixer, where the mixer blades must be within the product mixture.

BM10

DEFINITION Maximum product quantity that can be at the resource.

min_replenishmnt storage_unit

Quantity up to Which a Product Receipt is Allowed Stock Unit/sapapo/cres_min_replenishment /sapapo/cres_storage_unit


BN8


BO8


BN9

20

BO9

3

BN10

DEFINITION Specifies the product quantity in a container up to which a further receipt can occur. If the quantity at the resource is greater, and a further product receipt takes place, the system issues an alert, if you have entered the appropriate settings in the Alert Monitor profile. EXAMPLE If you want to configure a tank that must always be completely emptied before another product is added, you enter "0" as the remaining quantity allowed.

storage_unit_iso snplc

ISO code for unit of measurement Resource is not Relevant for SNP/sapapo/isocd_unit /sapapo/cres_snplc

char/ 3/ char/ 1/

BQ6


BP8

Valuetable: T006I

BP9

3

BQ9

1

BQ10

DEFINITION USE DEPENDENCIES If you implement block planning with buckets, you can only use a single mixed resource either in SNP or in block planning. If you want to use a resource in bucket-based block planning, you have to set the Not Relevant for SNP indicator. This constraint does not apply if you implement block planning without buckets. In this case, the bucket portion of the mixed resource is used by SNP. EXAMPLE

r3kapid r3arbid

Object ID of Capacity/Work Center in SAP R/3 Object ID of Capacity/Work Center in SAP R/3/sapapo/cres_r3objid /sapapo/cres_r3objid

numc/ 8/ numc/ 8/

BR9

8

BS9

8

add_plan_bucket dim_storage

Consider Bucket Capacity Dimension for Storage Characteristics of a Resource/sapapo/cres_add_plan_bucket /sapapo/cres_dimension_storage

char/ 1/ char/ 6/

BT6


BU8

Valuetable: T006D

BT9

1

BU9

6

util_bucket mix_plan_type

Rate of Bucket-Oriented Capacity Utilization (%) Defining Finite Capacity/sapapo/cres_util_bucket /sapapo/cres_mix_plan_type

dec/ 6/ 3 numc/ 1/

BV6


BW6

0 Time-Continuous Capacity 1 Bucket Capacity

BV9

7

BW9

1

BW10

DEFINITION Defines which capacity of the resource is to be used in Production Planning and Detailed Scheduling (PP/DS) - either the time-continuous capacity or the PP/DS bucket capacity. use dependencies You must set the indicator finite scheduling so that the resource can always be scheduled finitely. You have to select an appropriate scheduling mode in the Detailed Scheduling Strategy so that the system schedules the desired capacity finitely. If necessary, you can change the capacity to be scheduled finitely in the Detailed Scheduling Strategy. The setting in the detailed scheduling strategy of the Strategy Profile overrules the setting in the resource. If you set bucket capacity in the resource as finite capacity and you set time-continuous capacity in the strategy profile, then the time-continuous capacity of the resource is scheduled finitely.

campaign_ppds campaign_snp storage_to_zero

Resource is Campaign-Relevant Cross-Period Lot Size Handling the Remaining Fill Level/sapapo/cres_campaign_ppds /sapapo/cres_campaign_snp /sapapo/cres_storage_to_zero


BX6


BY6


BZ6


BX9

1

BY9

1

BZ9

1

BX10

DEFINITION You use this indicator to specify that the following requirements should be checked for the resource: The production campaign running on this resource must be uninterrupted, that is, the orders from a campaign must not be interrupted by an order that does not belong to the campaign. The setup order for this resource must be at the beginning of the campaign, and the clean-out order must be at the end of the campagin. DEPENDENCIES If a resource is campaign-relevant, it cannot be used as a secondary resource in a production process model (PPM). The system only checks the above campaign requirements for the resources if both the Campaign-Relevant indicator has been set in the resource master and the Consider Campaign Requirements indicator has been set in the strategy profile. You can override this setting by using the Consider campaign requirements indicator in the strategy profile. If you defined a resource as campaign-relevant, for example, but did NOT set the Consider Campaign Requirements indicator in the strategy profile, the system does not check the campaign requirements.

BY10

DEFINITION USE If you set this indicator, the SNP optimizer is able to execute cross-period lot size planning. During this planning, the SNP optimizer takes into account the setup statuses from the previous time bucket, if the same production process model (PPM) is used to produce a product. This means that the optimizer only schedules one setup operation. The system then calculates the setup costs and setup consumptions (fixed resource and material consumptions) that were defined in the PPM for a resource for which the Period Lot Size indicator has been set. DEPENDENCIES You must activate cross-period lot size planning in the SNP optimizer profile, meaning that you must enter a time horizon in the Cross-Period Lot Size field, over which the optimizer is to take into account the setup statuses from the previous time bucket, if the same PPM is being used to produce a product within this time bucket. The PPM that is taken into account by the SNP optimizer during planning must use this resource. The PPM is permitted to use a maximum of one resource for which the Period Lot Size indicator has been set. The PPM is not permitted to use any other resources with fixed resource consumption. The PPM duration must be less than or equal to the smallest bucket from the planning buckets profile being used. EXAMPLE

BZ10

DEFINITION This indicator controls the calculation and display of the fill level for the container resource . The decisive factor is whether or not the principle of product purity is to be followed. Product purity means that a container must not contain a mixture of different products. This indicator does not affect inventory management or pegging. If the indicator is not set, product purity is not taken into account. The system calculates the container resource's fill level from all material issues and receipts, irrespective of product purity. If product purity is violated, however, the system issues the Invalid mix alert. If the indicator is set, product purity must be taken into account. The fill level is represented as follows: If a new product that differs from the product still remaining in the container is filled into the container, the container resource's fill level is automatically set to zero. To inform the planner about the fact that there is still something left of another product in the container, the system issues the Quantity set to 0 alert. If a different product than the one in the container is to be discharged, however, the fill level is not set to zero. This means that product purity is not taken into account for material issues.

tsw_veh_id tsw_height tsw_width tsw_length tsw_draft_l

TD vehicle identifier Vehicle height Vehicle width Vehicle length Vehicle draught laden/sapapo/tsw_veh_id /sapapo/tsw_height /sapapo/tsw_width /sapapo/tsw_length /sapapo/tsw_draft_l

char/ 18/ quan/ 13/ 3 quan/ 13/ 3 quan/ 13/ 3 quan/ 13/ 3

CB8

Reference Table: BAPI10004RESHEAD Reference Field: TSW_L_UNIT

CC8


CD8


CE8


CA9

18

CB9

17

CC9

17

CD9

17

CE9

17

CA10

DEFINITION Alphanumeric identifier for a vehicle. The vehicle ID can be an external reference number, such as from the Vehicle Information System or the Dispatch Optimizer).

CB10

DEFINITION A value that represents the height of a vehicle.

CC10

DEFINITION A value that represents the width of a vehicle.

CD10

DEFINITION A value that represents the length of a vehicle.

CE10

DEFINITION A value which represents the draught of the ship, that is, the depth of the ship below the surface of the water. In this case the draught of the ship when it is loaded.

tsw_draft_u tsw_l_unit tsw_l_unit_iso tsw_speed_n

Vehicle draught unladen Unit of Measure ISO code for unit of measurement Vehicle normal speed/sapapo/tsw_draft_u /sapapo/unit /sapapo/isocd_unit /sapapo/tsw_speed_n

quan/ 13/ 3 unit/ 3/ char/ 3/ quan/ 13/ 3

CF8


CG8


CH8

Valuetable: T006I

CI8

Reference Table: BAPI10004RESHEAD Reference Field: TSW_SPEED_UNIT

CF9

17

CG9

3

CH9

3

CI9

17

CF10

DEFINITION A value which represents the draught of the ship, that is, the depth of the ship below the surface of the water. In this case the draught of the ship when it is unloaded.

CI10

DEFINITION A value that represents the normal speed of a vehicle.

tsw_speed_max tsw_speed_unit tsw_speed_unit_iso tsw_weight_unl

Vehicle maximum speed Unit of Measure ISO code for unit of measurement vehicle unladen weight/sapapo/tsw_speed_max /sapapo/unit /sapapo/isocd_unit /sapapo/tsw_weight_unl

quan/ 13/ 3 unit/ 3/ char/ 3/ quan/ 13/ 3

CJ8

Reference Table: BAPI10004RESHEAD Reference Field: TSW_SPEED_UNIT

CK8


CL8

Valuetable: T006I

CM8

Reference Table: BAPI10004RESHEAD Reference Field: TSW_WEIGHT_UNIT

CJ9

17

CK9

3

CL9

3

CM9

17

CJ10

DEFINITION A value that represents the maximum speed of a vehicle.

tsw_weight_unit tsw_weight_unit_iso tsw_carrier tsw_dummy_veh

Unit of Measure ISO code for unit of measurement External Location ID Dummy vehicle/sapapo/unit /sapapo/isocd_unit /sapapo/ext_locno /sapapo/tsw_dummy_veh


CQ6

X Yes No

CN8


CO8

Valuetable: T006I

CN9

3

CO9

3

CP9

20

CQ9

1

CP10


CQ10

DEFINITION You set this indicator, if you want a vehicle to be defined as a dummy vehicle. A dummy vehicle is used as a placeholder until the actual vehicle is known. Within TPVS, you can base your planning on a dummy vehicle just as you would for a real vehicle. When the real vehicle is known, you replace the dummy vehicle with a real vehicle.

tsw_pr_comp_grp tstream_external

Product vehicle resource compatibility group Capacity Data is From an External System/sapapo/tsw_pr_comp_grp /sapapo/cres_tstream_external

char/ 8/ char/ 1/

CS6


CR8

Conversion Exit: ALPHA

CR9

8

CS9

1

CS10

DEFINITION The indicator defines that the data that the system uses to determine the capacity of the resource (shift definitions, shift programs, and break models) is read directly from the connected R/3 system. USE If you have transferred the resource from a connected SAP R/3 system via the SAP APO Core Interface, and defined that the external capacity is to be used for the resources, then the system automatically sets the indicator and determines the available capacity for the resource from the data you maintained in the R/3 system. You must make the following settings in the R/3 system for SAP APO to use the external capacity of the resource: In Customizing of the R/3 system, choose Integration with Other mySAP.com Components ---> Advanced Planning and Optimization --> Application-Specific Settings and Enhancements --> Settings for Resources --> Set the Transfer of Resources to SAP APO and use the Use Ext.Capacity field to define that the external capacity is used either for all resources or only for specific resources. If you have defined that the external capacity is used only for specific resources, then you must set the External Capacity indicator for the APO data of the work center that you can maintain for the capacity header data. DEPENDENCIES The SAP APO CIF does not support any change transfer for shifts, shift programs, and breaks that you change in the R/3 system. SAP APO adjusts the available capacity of the resource to the changed data; this means that the available capacity is calculated again in SAP APO. SAP APO automatically schedules all orders that are affected by changes made to the shifts, breaks, and so on. The bucket portion of the capacity of a mixed resource can only be determined from the external system when you have specified that the bucket capacity is to be determined from the time-continuous capacity. EXAMPLE

resource_text

finity_level resuid resource

Finiteness Level of the Resource Resources GUID (Length 32) External Name of Resource/sapapo/cres_finity_level bapi10004resid_32 bapi10004ext_resname


CU4

MEANING Transfer parameter for language-dependent short texts. RANGE Key fields: "Resource" or "Resuid" "Langu" or "LanguIso" HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

CT8

Valuetable: /SAPAPO/FINLEVL

CT9

4

CU9

32

CV9

40

CT10

DEFINITION USE If the resource is used by several applications, you can use the finiteness level to define which application schedules the resource finitely and which schedules infinitely. DEPENDENCIES You define the finiteness levels that you can assign in the SAP APO implementation guide (IMG) under Advanced Planning and Optimization -> Master Data -> Resource -> Define Finiteness Levels for Resources. If you do not assign any finiteness level to the resource, the default value 0 is valid. In the settings for each application (for example, in the strategy profile), you specify the maximum finiteness level up until which resources should be scheduled finitely. hints The maximum possible value is 9999. If you enter this value, only the applications in which the finiteness level is also 9999 schedule the resource finitely. If you enter the value 0, all applications in which finite scheduling is set schedule these resources finitely, irrespective of the finiteness level defined there. EXAMPLE The resource R1 is used in Production Planning (PP) (for example, in the production planning run), and in Detailed Scheduling (DS) (for example, in the DS planning board). You have defined the following finiteness levels in Customizing: Finiteness level,, Short description 0,, Finite for all applications (default) 100,, For PP finite resource 200,, For DS finite resource 300,, For PP/DS optimization finite resource 9999,, Restricted finite resource In PP the resource should be scheduled infinitely, and in DS it should be scheduled finitely. You enter the finiteness level 200 at the resource R1. In the PP strategy profile, you define that only resources with a finiteness level smaller than or equal to 100 should be scheduled finitely. In the DS strategy profile, you enter 200 for this value. PP therefore schedules infinitely on R1, while DS schedules finitely.

CU10


CV10


CV11


resource_quanmodel

langu langu_iso res_short_text resuid

Language Key Language according to ISO 639 Short Description Resources GUID (Length 32)langu laiso /sapapo/cres_text bapi10004resid_32

lang/ 1/ char/ 2/ char/ 60/ char/ 32/

CZ4

MEANING Transfer parameter for assignments to quantity/rate definitions. RANGE Key fields: "Resource" or "Resuid" "Version" "Endda"

CW8


CW9

2

CX9

2

CY9

60

CZ9

32

CW10


CZ10


resource version

External Name of Resource Number for the Available Capacity Variant of the Resourcebapi10004ext_resname /sapapo/cres_version

char/ 40/ numc/ 2/

DB8


DA9

40

DB9

2

DA10


DB10

DEFINITION USE You can create up to 99 capacity variants for each resource. You specify an active variant in the resource header. DEPENDENCIES For optimization in SNP, you define a variant with a minimum, medium and maximum capacity.

DA11


endda begda quanmodel facdayind

Valid Until' Date Valid From' Date Name of Quantity/Rate Definition Workdays/sapapo/cres_endda /sapapo/cres_begda /sapapo/cres_quan_name /sapapo/cres_facdayind

dats/ 8/ dats/ 8/ char/ 40/ char/ 1/

DF6

Workdays According to the Factory Calendar 0 Non-Workdays (Overrides Factory Calendar) 1 Workdays (Overrides Factory Calendar)

DC9

10

DD9

10

DE9

40

DF9

1

DC10

DEFINITION Specifies when the validity finishes.

DD10

DEFINITION Specifies when the validity starts.

DE10

DEFINITION Defines the capacity of the resource using quantities or rates. For the quantities, you can alternatively: Refer to a particular number of days thereby, for example, describing the usage production or usage rate for the resource Enter without time reference thereby, for example, describing the transport or storage capacity for the resource. use You use a quantity/rate definition to define the quantity capacity or rate in the time intervals for the capacity variants. To do this, you enter time intervals in a capacity variant and assign each time interval a quantity/rate definition.

DF10

DEFINITION Specifies whether the days in the interval are workdays, non-workdays, or workdays according to the factory calendar. The following options are available: The factory calendar determines workdays and non-workdays (blank). All the days in the interval are workdays (1). All the days in the interval are non-workdays (2). dependencies You enter the factory calendar in the resource header. The SNP optimizer does not take this field into consideration during planning. It takes into account the entries in the field when calculating the available capacity of the capacity variant but always uses the factory calendar during planning.

resource_shiftseq

util_bucket resuid

Rate of Bucket-Oriented Capacity Utilization (%) Resources GUID (Length 32)/sapapo/cres_util_bucket bapi10004resid_32

dec/ 6/ 3 char/ 32/

DH4

MEANING Transfer parameter for assignments to shift sequences. RANGE Key fields: "Resource" or "Resuid" "Version" "Endda"

DG6


DG9

7

DH9

32

DH10


resource version

External Name of Resource Number for the Available Capacity Variant of the Resourcebapi10004ext_resname /sapapo/cres_version

char/ 40/ numc/ 2/

DJ8


DI9

40

DJ9

2

DI10


DJ10


DI11


endda begda facdayind shiftseq

Valid Until' Date Valid From' Date Workdays Name of Shift Sequence/sapapo/cres_endda /sapapo/cres_begda /sapapo/cres_facdayind /sapapo/cres_timemodel_name

dats/ 8/ dats/ 8/ char/ 1/ char/ 40/

DM6

Workdays According to the Factory Calendar 0 Non-Workdays (Overrides Factory Calendar) 1 Workdays (Overrides Factory Calendar)

DK9

10

DL9

10

DM9

1

DN9

40

DK10


DL10


DM10

DEFINITION Specifies whether the days in the interval are workdays, non-workdays, or workdays according to the factory calendar. The following options are available: The factory calendar determines workdays and non-workdays (blank). All the days in the interval are workdays (1). All the days in the interval are non-workdays (2). dependencies You enter the factory calendar in the resource header. The SNP optimizer does not take this field into consideration during planning. It takes into account the entries in the field when calculating the available capacity of the capacity variant but always uses the factory calendar during planning.

DN10

DEFINITION In a shift sequence, you define the daily shift order for as many consecutive days as you want. use You use shift sequences to define the working times and the capacity in the capacity variants for a resource. To do this, you define in each capacity variant time intervals and: Assign each time interval a shift sequence Define which day of the shift sequence falls on the first day of the time interval The shift sequence repeats itself in cycles, for example, every 5 days for a 5-day shift sequence. dependencies You construct shift sequences with the help of shift definitions.

doffset timeeff

First Day of Shift Sequence in the Time Interval Name of Shift Factor Definition/sapapo/cres_offset /sapapo/cres_timeeff_name

numc/ 2/ char/ 40/

DO9

2

DP9

40

DO10

DEFINITION Specifies which day of the shift sequence falls on the first day of the interval. EXAMPLE You have defined a four day shift sequence. If you enter 2 for the first day, the first day of the time interval has the shifts from the second day of the shift sequence.

DP10

DEFINITION In a shift factor definition you define: The rate of resource utilization The capacity, for example, The maximum width of an object that a saw can process The number of machines or people working on the resource The capacity is relevant for multi-activity resources. Only the productive time is relevant for single activity resources; these resources have capacity 1 without a unit of measurement. use When you create a shift definition, assign it a shift factor definition.

resource_downtime

resuid resource begda

Resources GUID (Length 32) External Name of Resource Valid From' Datebapi10004resid_32 bapi10004ext_resname /sapapo/cres_begda

char/ 32/ char/ 40/ dats/ 8/

DQ4

MEANING Transfer parameter for defining downtimes. RANGE Key fields: "Resource" or "Resuid" "Begda" "Begti"

DQ9

32

DR9

40

DS9

10

DQ10


DR10


DS10


DR11


begti endda endti

Start of Downtime Valid Until' Date End of Downtime/sapapo/cres_begti_down_disp /sapapo/cres_endda /sapapo/cres_endti_down_disp

tims/ 6/ dats/ 8/ tims/ 6/

DT9

8

DU9

10

DV9

8

DT10

DEFINITION Specifies the time at which a downtime starts. USE During downtime, the resource is not available, and can therefore not be scheduled during this time period.

DU10


DV10

DEFINITION Defines the time when the downtime ends. USE During downtime, the resource is not available, and can therefore not be scheduled in this time period.

downtime_type downtimeid pm_ordid

Type of Downtime Downtime GUID (length 32) Order GUID (Length 32) for Downtime/sapapo/cres_downtime_type bapi10004downtimeid_32 bapi10004downtimeordid_32


DW6

01 Planned Downtime 02 Resource is Inactive 03 PM Order

DW9

2

DX9

32

DY9

32

DW10

DEFINITION You use this to differentiate between two categories of downtime: Planned downtime (for example, due to maintenance) can be changed, added or deleted in a simulation. When adopting the simulation into the planning version, the planned downtimes are copied from the simulation and the planned downtimes in the planning version are deleted. Downtime due to a resource breakdown cannot be changed in a simulation. It is always copied from the planning version data into the simulation. When adopting the simulation, these downtimes remain constant.

DX10

MEANING Downtime GUID (length 32). HINTS GUID definition GUIDs are usually created in the APO system. In some interfaces, a GUID can also be taken from an external system. In this case, the GUID must be generated using the specified algorithm (some programming languages provide their own APIs). It is not possible to generate the GUID again (for example, with user-defined characters). Display Format of the GUID: CHAR32 A 128 bit GUID corresponds to 16 Bytes. For CHAR32 display, each byte is displayed as two hexadecimal numbers. This results in 16 * 2 = 32 characters. The display is made using capital letters because this is the usual transfer format and is used in most interfaces. CHAR22 A 128 bit GUID corresponds to 16 Bytes. For CHAR22 display, each byte is converted into a CHAR22 character string using a special algorithm. The display contains lower case and capital letters. RAW16 Display using 16 Byte.

DY10

DEFINITION Order GUID (length 32) of the assigned maintenance order. HINTS GUID definition GUIDs are usually created in the APO system. In some interfaces, a GUID can also be taken from an external system. In this case, the GUID must be generated using the specified algorithm (some programming languages provide their own APIs). It is not possible to generate the GUID again (for example, with user-defined characters). Display Format of the GUID: CHAR32 A 128 bit GUID corresponds to 16 Bytes. For CHAR32 display, each byte is displayed as two hexadecimal numbers. This results in 16 * 2 = 32 characters. The display is made using capital letters because this is the usual transfer format and is used in most interfaces. CHAR22 A 128 bit GUID corresponds to 16 Bytes. For CHAR22 display, each byte is converted into a CHAR22 character string using a special algorithm. The display contains lower case and capital letters. RAW16 Display using 16 Byte.

resource_downtime_text

resuid resource begda

Resources GUID (Length 32) External Name of Resource Valid From' Datebapi10004resid_32 bapi10004ext_resname /sapapo/cres_begda

char/ 32/ char/ 40/ dats/ 8/

DZ4

MEANING Transfer parameter for defining short texts for downtimes. RANGE Key fields: "Resource" or "Resuid" "Begda" "Begti" "Langu" or "LanguIso" HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

DZ9

32

EA9

40

EB9

10

DZ10


EA10


EB10


EA11


begti langu langu_iso text

Start of Downtime Language Key Language according to ISO 639 Short Description/sapapo/cres_begti_down_disp langu laiso /sapapo/cres_text

tims/ 6/ lang/ 1/ char/ 2/ char/ 60/

ED8


EC9

8

ED9

2

EE9

2

EF9

60

EC10

DEFINITION Specifies the time at which a downtime starts. USE During downtime, the resource is not available, and can therefore not be scheduled during this time period.

ED10


resource_model

resuid resource

Resources GUID (Length 32) External Name of Resourcebapi10004resid_32 bapi10004ext_resname

char/ 32/ char/ 40/

EG4

MEANING Transfer parameter for model assignments. If the "RemoveFlag" indicator is set for an assignment entry, the version-independent resource is removed from the model specified. HINTS A resource can only be removed from a model if it is no longer being used in this model (a check for usage is made automatically). Note also that if you remove the version-independent resource from a model, this may also lead to the automatic deletion of the corresponding version-dependent resource.

EG9

32

EH9

40

EG10


EH10


EH11


model remove_flag

Model Name (Copy from /SAPAPO/C_MODELID) Select an Option (Yes = 'X', No = ' ')/sapapo/cres_modelid bapiyesno

char/ 22/ char/ 1/

EJ6

No X Yes

EI9

22

EJ9

1

EI10

DEFINITION Key that uniquely identifies a supply chain model

resource_ratemodel

resuid resource

Resources GUID (Length 32) External Name of Resourcebapi10004resid_32 bapi10004ext_resname

char/ 32/ char/ 40/

EK4

MEANING Transfer parameter for assignments to rate models. RANGE Key fields: "Resource" or "Resuid" "Version" "Endda"

EK9

32

EL9

40

EK10


EL10


EL11


version endda begda

Number for the Available Capacity Variant of the Resource Valid Until' Date Valid From' Date/sapapo/cres_version /sapapo/cres_endda /sapapo/cres_begda

numc/ 2/ dats/ 8/ dats/ 8/

EM8


EM9

2

EN9

10

EO9

10

EM10


EN10


EO10


ratemodel

Name of Rate Model/sapapo/cres_rate_name

char/ 40/

EP9

40

EP10

DEFINITION Determines the production rates of a production line resource for various time periods. USE You can define several production rates with various validity periods in a rate model. You can enter the end of the validity period. The system determines the start of the validity period based on the end validity date of the preceding production rate. dependencies When you have defined a rate model, you can choose capacity variants based on the header data and then assign it in the tab page Cap.Var Rate to a production line resource.

logical_system

logical_system


-> documentation

char/ 10/

A1

bapi_ppmsrvaps_savemulti_30a

B1

bapi_ppmsrvaps_getlist

A2

FUNCTIONALITY Using this method, you can create, change, or enhance production process model plans. HINTS If a production process model or plan does not yet exist, the system creates it automatically. If it already exists, it is enhanced or changed. For more information, see the documentation for the "AutoDelete" parameter. Warning: For the transfer of SNP and SP plans, you need to ensure that the "Cp_Date_to" field is filled in the "Logical_Component" table and the "Comp_Product_Tdpp" table to correspond with the "Date_To" field in the "Comp_Product" table, to which the entries refer. In addition, the "Log_Component" field always corresponds to the product number for this planning. For PP/DS plans, the "CP_Date_To" field in the "Logical_Component" and "Comp_Product_Tdpp" tables is not important and so can be ignored. When this method is executed, no database locks are set and evaluated, since the interface has highest priority. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information

B2

FUNCTIONALITY You can use this method to read production process models PPMs or plans for certain selection criteria. EXAMPLE HINTS You can choose from the following options for selecting plans. Combinations between alternatives are either not possible, or are ignored by the system. Selection by specifying plan GUIDs: "PlanGuids" Selection using RANGES tables: You can use one of the following combinations here: "PlanSelection" "LocationSelection" + "ProductSelection" Selection using an explicit key: "PlanKey" Note that the logical system (or the business system group) must also be given for all selection variants. For more information, see the documentation for the individual parameters. FURTHER_SOURCES_OF_INF General information

B4


B8


B9

10

B10


auto_delete business_check

auto_delete business_check

Automatic Deletion of PPM/Plan by Data Transfer Execute Extended Checksbapi10003autodel bapi10003businesscheck

char/ 1/ char/ 1/

C4

MEANING If a PPM or plan already exists and you set the "AutoDelete" import parameter to "X", first the complete PPM or plan is deleted and then it is recreated with the data specified. You should note that the new PPM has the same "PpmId" as the PPM that was deleted. Orders that already exist that were exploded using the PPM that has been deleted are exploded again using the new PPM as soon as a change relevant to explosion is made. If this parameter is not set, the PPM or plan that already exists is changed or enhanced according to the data specified.

D4

MEANING If this parameter is set, additional business checks are carried out as well as the technical consistency checks. The messages are also returned in the "Return" parameter. Note, however, that the additional checks may hinder performance. RANGE DEFAULT

C6

No X Yes

D6

No X Yes

C9

1

D9

1

C10

DEFINITION This switch can be used to indicate whether the PPM/plan data should be deleted automatically or not. FALSE (' ') If a plan or PPM already exists, it is either extended (for example when new operations are transferred) or changed (for example when an existing operation is transferred). Data is not deleted from the PPM. TRUE ('X') If you enter this value, the entire PPM and the plan that belongs to it will be deleted and replaces by the new data transferred. This means that if there are already five operations in a plan, and only two operations are transferred during a transfer, all five will be deleted and replaced by the two new operations. When you use this option, it is expected that the entire plan/PPM is transferred. Attention: This transfer method should not be selected if only part of the data in an existing PPM should be changed. Otherwise all the rest of the PPM data could be deleted.

D10

DEFINITION If this parameter is set additional business checks are executed along with the technical consistency checks. However, please note that the additional checks may lead to a drop in performance.

plan

plan_number single_level_cost_var

External Name of Plan in Production Process Model Single-Level Costs (Variable)/sapapo/ext_plannr /sapapo/cost1

char/ 60/ int4/ 10/

E4

MEANING Transfer parameter for general planning data. RANGE Key fields: PlanNumber

E9

60

F9

10

F10

DEFINITION Variable (that is, quantity-dependent) costs that are incurred when this production process model is used. The costs incurred in staging the components are not included in this parameter.

E11

BAPI10003PPMHELP/PLAN_EXT

single_level_cost_fix plan_state plan_usage

Single-Level Costs (Fixed) Status of a Plan in Production Process Model Use of a Plan/sapapo/cost2 /sapapo/state /sapapo/plan_usage

int4/ 10/ char/ 1/ char/ 1/

H6

0 Inactive 1 Active

I6

S PPM for Supply Network Planning (SNP) P PPM for Production Planning and Detailed Scheduling (PP/DS) T Template PPM D BOM for Demand Planning (DP)

G9

10

H9

1

I9

1

G10

DEFINITION Fixed, that is, quantity-dependent costs which are incurred when using this production process model, for example, when setting up. The costs incurred for retrieving components are not contained in these parameters.

I10

DEFINITION USE A PPM plan for PP/DS (PP/DS-PPM) contains data on the duration of the individual worksteps that is accurate to the second. In a PPM plan for SNP (SNP-PPM), you can only specify the activities in buckets. You can also only assign one mode. A PPM plan for DP (DP-PPM) corresponds to a bill of materials in SAP R/3 and contains no information on resources. You can use a template PPM (plan usage T) for the method CreateFromTemplate of the Business Application Programming Interface (BAPI) ManufactOrderAPS. For more information, refer to the documentation of the function module BAPI_MOSRVAPS_SAVETMPLPPM. DEPENDENCIES The usage types are fixed values. EXAMPLE

multi_level_cost_fix multi_level_cost_var

Costs: Multi-Level (Fixed) Costs: Multi-Level (Variable)/sapapo/ppm_cost_fix /sapapo/ppm_cost_var

int4/ 10/ int4/ 10/

J9

10

K9

10

J10

DEFINITION Fixed costs, that is, quantity-independent costs, which result from using this production process model. The fixed portion of costs, which result from the staging of components, are contained in this parameter. Use This parameter is used for the scheduling heuristic in PP/DS. If there is a shortage of a product, all possible sources of supply are first determined. These sources are sorted according to their costs. The sources of supply with the lowest costs are checked first. If the product can be obtained from this source on time, the search terminates. If this is not possible, the source with the next lowest costs is checked.

K10

DEFINITION Variable, that is, quantity-dependent cost, that derives from using this production process model. The variable portion of the costs, which results from staging the components, is contained in these parameters. Use These parameters are used for the scheduling heuristic in PP/DS. If there is a shortage of a product, the system first determines all possible sources of supply. Sources include transporation lanes and the production process model. These are sorted according to their costs. The source of supply with the lowest costs is first checked. If the product can be taken from this source on time, the system terminates the search. If this is not possible, the system checks the next source with the lowest costs.

rel_plannr

External Name of Plan in Production Process Model/sapapo/ext_plannr

char/ 60/

L9

60

cosnr

Supply Network Planning: External Cost Function/sapapo/snpcosex

char/ 10/

M9

10

M10

Use Cost functions are used by optimization-based planning in Supply Network Planning (SNP), to calculate the costs of procuring, producing, and transporting varying quantities of products. The following types of cost function are available: The cost function in the location product master defines the cost of procurement. The cost function in the production process model (PPM) or in the production data structure (PDS) defines the costs of production. The cost function in the master data of the transportation lane defines the transportation costs. Example You specify a quantity interval of 22,000 to 33,000 pieces with a fixed cost of 44,000 and a variable cost of 10. The quantity the SNP optimizer recommends for procurement, production, or transportation is 25,000 pieces. The system calculates the costs as follows: 44,000 + 10 x (25,000 - 22,000) Dependencies You define the cost functions using the Maintain pushbutton.

plan_text

plan_number langu langu_iso

External Name of Plan in Production Process Model Language Key Language according to ISO 639/sapapo/ext_plannr langu laiso

char/ 60/ lang/ 1/ char/ 2/

N4

MEANING Transfer parameter for language-dependent plan texts. RANGE Key fields: PlanNumber Langu LanguIso HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

O8


N9

60

O9

2

P9

2

O10


N11


ppm

text ppm_number log_component

Plan Description Production Process Model: External Number Logical Component/sapapo/plntxt /sapapo/ext_ppmnr /sapapo/logcomp


R4

MEANING Transfer parameter for production process models. RANGE Key fields: PpmNumber HINTS The "PpmNumber" must be unique on a cross-plan basis. The "LogComponent", "Product", and "DateTo" fields must always refer to an entry in the "CompProduct" table. That is, an entry must exist in the "CompProduct" parameter for the values mentioned above for the current plan.

Q9

40

R9

60

S9

40

S10

DEFINITION A logical component combines various technical alternatives of a material component that have different temporal validities. For example, a component is valid in a specific period. After a technical change has been made, a different component is valid. Example: PC A PENTIUM processor is currently being installed. In six months, however, a PENTIUM II will be installed. The logical component could be, for example, a CPU.

product location loctype

External Product Indicator External Location ID Location Type/sapapo/ext_matnr /sapapo/ext_locno /sapapo/c_loctype


V6


T8


T9

40

U9

20

V9

4

T10


U10


V10


T11


U11


plan_number date_from date_to

External Name of Plan in Production Process Model Validity per. start Validity period end/sapapo/ext_plannr /sapapo/datef /sapapo/datet

char/ 60/ dec/ 15/ 0 dec/ 15/ 0

W9

60

X9

19

Y9

19

W11


min_lsz max_lsz source_priority disc_ppm_flg

Minimum Lot Size Maximum Lot Size Procurement Priority SNP Optimizer: Discretize PPM/sapapo/minls /sapapo/maxls /sapapo/tr_sprio /sapapo/snppdisc

quan/ 15/ 3 quan/ 15/ 3 dec/ 15/ 2 char/ 1/

AC6

X TRUE FALSE

Z8

Reference Table: /SAPAPO/MATKEY Reference Field: MEINS

AA8

Reference Table: /SAPAPO/MATKEY Reference Field: MEINS

Z9

20

AA9

20

AB9

20

AC9

1

Z10

USE You define a lot size interval using the minimum and maximum lot sizes. The use of the lot size interval depends on the application, as follows: Interactive planning, and planning with heuristics in SNP and in PP/DS With the lot size interval, you specify for which order quantities the production process model (PPM) can be used if you are planning interactively or with heuristics in Supply Network Planning (SNP) or in Production Planning and Detailed Scheduling (PP/DS). The system can only use a PPM to create an order if the order quantity is between the minimum and maximum lot sizes. The minimum lot size is the smallest quantity that can be produced with this PPM. The maximum lot size is the largest quantity that can be produced with this PPM. Note: You define the minimum or maximum quantity of a PP/DS order using the minimum and maximum lot sizes in the location product master. SNP Optimizer Using the lot size interval, you specify the restrictions for the quantity to be produced in a planning period. The SNP optimizer must adhere to these restrictions if it uses the production process model as a source of supply. The minimum lot size is the minimum quantity that can be produced in a planning period (if anything is to be produced during the planning period). With lot size planning a cross-period lot size must be at least as large as the minimum lot size. The maximum lotsize is the maximum quantity that can be produced per day. If you use a planning period other than day for the planning, the SNP optimizer uses this value to automatically calculate the maximum quantity to be produced in the planning period. The maximum lot size specified in the product master is not relevant for the SNP optimizer. In the optimization profile, you specify if the SNP optimizer should consider the minimum or the maximum lot size. note When using mixed resources, you can integrate SNP and PP/DS and convert the orders created by SNP into PP/DS orders. The SNP order can specify the source of supply with which the PP/DS orders should be created; to do this, enter the PP/DS PPM to be used in the SNP PPM. Note that in this context, the PP/DS and SNP optimizers interpret the lot size intervals differently and reconcile the PPM lot size intervals with each other accordingly. For more information, see Recommendations for determining lot size intervals for an SNP PPM.

AA10

USE You define a lot size interval using the minimum and maximum lot sizes. The use of the lot size interval depends on the application, as follows: Interactive planning, and planning with heuristics in SNP and in PP/DS With the lot size interval, you specify for which order quantities the production process model (PPM) can be used if you are planning interactively or with heuristics in Supply Network Planning (SNP) or in Production Planning and Detailed Scheduling (PP/DS). The system can only use a PPM to create an order if the order quantity is between the minimum and maximum lot sizes. The minimum lot size is the smallest quantity that can be produced with this PPM. The maximum lot size is the largest quantity that can be produced with this PPM. Note: You define the minimum or maximum quantity of a PP/DS order using the minimum and maximum lot sizes in the location product master. SNP Optimizer Using the lot size interval, you specify the restrictions for the quantity to be produced in a planning period. The SNP optimizer must adhere to these restrictions if it uses the production process model as a source of supply. The minimum lot size is the minimum quantity that can be produced in a planning period (if anything is to be produced during the planning period). With lot size planning a cross-period lot size must be at least as large as the minimum lot size. The maximum lotsize is the maximum quantity that can be produced per day. If you use a planning period other than day for the planning, the SNP optimizer uses this value to automatically calculate the maximum quantity to be produced in the planning period. The maximum lot size specified in the product master is not relevant for the SNP optimizer. In the optimization profile, you specify if the SNP optimizer should consider the minimum or the maximum lot size. note When using mixed resources, you can integrate SNP and PP/DS and convert the orders created by SNP into PP/DS orders. The SNP order can specify the source of supply with which the PP/DS orders should be created; to do this, enter the PP/DS PPM to be used in the SNP PPM. Note that in this context, the PP/DS and SNP optimizers interpret the lot size intervals differently and reconcile the PPM lot size intervals with each other accordingly. For more information, see Recommendations for determining lot size intervals for an SNP PPM.

AB10

DEFINITION The priority of a source of supply in source determination. The highest priority is priority 0. &USE& In Production Planning and Detailed Scheduling, the system uses additional criteria for source determination, such as costs. If the procurement priority is the same, the system selects the source with the lower costs. For Deployment, you use the procurement priority to determine the sequence of source locations from which the Realtime Deployment is started, if you are using this for a target location.

AC10

DEFINITION USE You use this indicator during optimization-based planning in Supply Network Planning (for individual production process models) to set it so that this PPM is only executed in integer multiples of the lot size within the discretization horizon. The indicator is used mostly to exclude individual PPMs from being discretized, as the discretization procedure reduces the solution-finding capabilities in SNP optimization-based planning. DEPENDENCIES You must activate indicator discrete PPM in the SNP optimizer profile. You use this indicator mainly to define that the PPMs taken into account by the SNP optimizer during planning should be discretized. You also define the discretization horizon here. EXAMPLE

bucket_rnd_value

Bucket Offset for Product Availability during Production/sapapo/snprndprp

dec/ 3/ 2

AD9

4

AD10

DEFINITION Factor used by the SNP optimizer to calculate the availability date of a receipt element within a period (bucket). USE If a product is available in the middle of a bucket, the system must know if the product can be used at the start of this bucket or at the end of this bucket (which is the same as at the start of the next bucket). For this purpose, the system uses two rounding limits, one for transported products and one for produced products. These rounding limits are used in the following way: First the system evaluates the relevant calendars to determine the exact availability date of the products. Then, the length of the bucket based on this date is multiplied by the percentage specified in this field, to calculate the rounding limit within this bucket. If the exact availability date lies before or at the rounding limit, the product is available at the start of the bucket; if not, the product is available at the start of the next bucket. Rule of thumb: Greater values represent an optimistic view because they imply that the products tend to be available earlier than specified. Smaller values represent a more conservative view because they imply that the products are guaranteed to be available. DEPENDENCIES If you enter a value for the bucket offset in the PPM master data, this value overwrites the value entered in the SNP optimizer profile. The SNP heuristic does not consider the bucket offset. EXAMPLE

preq_cover_type source_location source_loctype

Period Factor for Calculating the Availability Date/Time External Location ID Location Type/sapapo/rrp_req_cover_type /sapapo/ext_locno /sapapo/c_loctype

dec/ 4/ 3 char/ 20/ char/ 4/

AE6

0.000 Factor for Availability Date Within the Period

AG6


AE9

5

AF9

20

AG9

4

AE10

DEFINITION Factor used by the system to calculate the availability date/time of a receipt element within a time period (bucket). USE The system determines the exact availability date/time of the receipt elements within a period, by adding a time interval (that it gets by multiplying the period factor with the period length) to the start time of the period. You can enter a factor between 0 and 1, where 0 is the start of the period, 0.5 the middle, and 1 the end of the period. When calculating the availability date/time, the system takes into consideration all weekdays, meaning that it does not take into consideration any days that have been defined as non-workdays in the calendars. The following applications can take the period factor into account: Heuristic in Supply Network Planning (SNP) The SNP optimizer does not consider any period factor. Period lot-sizing procedure in Production Planning and Detailed Scheduling (PP/DS) Usage in the SNP Heuristic The system uses the period factor to calculate the availability date . It sets the availability time automatically to 12:00 within daily buckets. The following period factors are relevant for the SNP heuristic: Period factor in the location product master In order that the SNP heuristic can take the period factor into consideration, you have to set the Use Period Factor indicator. If you do not set the indicator, the system always uses the standard value 0.5 for the period factor. Period factor in the production process model or in the transportation lane If you have defined a value for the Period Factor for the SNP heuristic in a production process model (PPM) or in a transportation lane, the system first considers this value when calculating the availability date/time. The period factor in the production process model is only relevant for in-house production orders, while the period factor in the transportation lane is only relevant for external procurement orders. If, in the PPM or in the transportation lane you have not defined a value, the system checks if you have set the Period Factor indicator in the location product master. If this is the case, the system takes the value defined in the Period Factor field of the location product master into consideration. If neither parameter has been maintained in the location product master, the system uses the standard value 0.5, meaning that it sets the availability date/time to the middle of the period. Usage in the PP/DS Period Lot-Sizing Procedure In order that PP/DS can consider the period factor from the location product master in the period lot-sizing procedure, you have to set the Use Period Factor indicator. The system calculates the availability date/time from the period duration, to the exact second. If , for example, you specify 0.75 for the period factor, for a period duration of one day, the availability time is 18:00. The period factor in the production process model or in the transportation lane is not relevant to PP/DS. EXAMPLE

AF10


AG10


ppm_text

ppm_number langu langu_iso

Production Process Model: External Number Language Key Language according to ISO 639/sapapo/ext_ppmnr langu laiso

char/ 60/ lang/ 1/ char/ 2/

AH4

MEANING Transfer parameter for language-dependent PPM texts. RANGE Key fields: PpmNumber Langu LanguIso HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

AI8


AH9

60

AI9

2

AJ9

2

AI10


operation

text plan_number

PPM Description External Name of Plan in Production Process Model/sapapo/ppmtxt /sapapo/ext_plannr

char/ 40/ char/ 60/

AL4

MEANING Transfer parameter for operations. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension HINTS Note that the operation number consists of two parts. The "OperationNumber" must always be filled but the "OperationNumberExtension" can generally be left empty. The "OperationNumberExtension" is usually filled for plans that were created using the Core Interface. In this case, the "OperationNumberExtension" must always be specified when changing these operations.

AK9

40

AL9

60

AL11


operation_number operation_number_extension setup_group

Operation Number Extension of Operation number (R/3) Setup Group/sapapo/cdps_operation_number bapi10003r3oprnumextension /sapapo/cdps_setup_group


AM9

4

AN9

8

AO9

40

AO10

DEFINITION Name of the setup group

setup_item setup_location setup_loctype stat_split_capacity

Setup Key External Location ID Location Type Statistical split quantity/sapapo/cdps_setup_item /sapapo/ext_locno /sapapo/c_loctype /sapapo/stat_split_capa

char/ 40/ char/ 20/ char/ 4/ quan/ 13/ 3

AR6


AS8

Reference Table: BAPI10004RESHEAD Reference Field: NOINDIVRES_UNIT

AP9

40

AQ9

20

AR9

4

AS9

17

AP10

DEFINITION Indicates a setup status within a setup group. use With setup groups you can carry out a rough classification of setup statuses. If you want to classify differentiated setup statuses within the setup group, you must define a setup key for the setup group. Each setup key should only be avaiable in exactly one setup group for the location.

AQ10


AR10


AS10

DEFINITION This functionality is not currently available.

operation_text

operation_type super_operation plan_number

Operation Type Operation Number External Name of Plan in Production Process Model/sapapo/vrgtyp /sapapo/vornr /sapapo/ext_plannr

int1/ 3/ char/ 12/ char/ 60/

AV4

MEANING Transfer parameter for language-dependent operation texts. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Langu LanguIso HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

AT6

0 PP operation 1 PI operation 2 PI phase 3 PP/PI suboperation

AT9

3

AU9

12

AV9

60

AT10

DEFINITION The operation type provides information on the work plan / recipe objects from the R/3. These objects represent the operation. The operation type is automatically set during the transfer of the plan / recipe from the SAP R/3 system. 0 represents an operation from a work plan. 1 represents an operation from a recipe - this operation never has an activity in PPM, a dummy activity exists in the PDS. 2 represents a phase and always has exactly one activity. 3 represents a suboperation for a work plan or a secondary resource for a recipe. The operation always has exactly one activity.

AV11


operation_number operation_number_extension langu

Operation Number Extension of Operation number (R/3) Language Key/sapapo/cdps_operation_number bapi10003r3oprnumextension langu

char/ 4/ char/ 8/ lang/ 1/

AY8


AW9

4

AX9

8

AY9

2

AY10


langu_iso text

Language according to ISO 639 Operation Descriptionlaiso /sapapo/acttxt

char/ 2/ char/ 40/

AZ9

2

BA9

40

activity

plan_number operation_number

External Name of Plan in Production Process Model Operation Number/sapapo/ext_plannr /sapapo/cdps_operation_number

char/ 60/ char/ 4/

BB4

MEANING Transfer parameter for planning activities. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity HINTS To set scrap at 10%, for example, the "Scrap" field must be filled with the value "0.1000".

BB9

60

BC9

4

BB11


operation_number_extension activity scrap activity_type

Extension of Operation number (R/3) Activity Number Scrap Factor Activity Typebapi10003r3oprnumextension /sapapo/actnr /sapapo/scrap /sapapo/acttype

char/ 8/ char/ 40/ dec/ 5/ 4 char/ 1/

BG8

Valuetable: /SAPAPO/ACTTYPC

BD9

8

BE9

40

BF9

6

BG9

1

BE10

DEFINITION A number that can be freely selected and assigned to the activity. USE DEPENDENCIES EXAMPLE

setup_flg tdpp_flg

Setup Activity with Sequence-Dependent Duration Time-Dependent Parameters Maintained/sapapo/setup /sapapo/tipp

char/ 1/ char/ 1/

BH6

X Yes No

BI6

X TRUE FALSE

BH9

1

BI9

1

BH10

DEFINITION Specifies that the duration of the setup activity is dependent on which operation was processed at the resource prior to this, that is, it is dependent on the current setup status of the resource. use When you set this indicator the system, during DS planning or or setup optimization, determines the setup duration for the setup matrix you assigned to the resource You can only adjust the setup time for single resources dependencies You characterize the setup status necessary for processing the operation using the setup group or setup key that you enter for the operation. You may only set the indicator for setup activities, that is, for activities with the activity type S.

BI10

DEFINITION Indicates that time dependent planning parameters are maintained in the production process model (PPM) for this object . hints In PPM you can maintain planning version dependent and time dependent planning parameters for the following PPM objects: PPM Object ,, planning parameters Activity ,, scrap Mode ,, variable and fixed activity period Resource ,, variable and fixed resource consumption of the activity Components ,, variable and fixed consumption During PPM explosion the system consumes the planning parameters which are valid at that time.

synchronization effectivity

Synchronization Behavior Validity Mode/sapapo/nosyncflg /sapapo/om_effectivity_mode

char/ 1/ int1/ 3/

BJ6

Synchronization behaviour defined in the resource R Overrule synchronization behaviour

BK6

0 Activity must lie within effectivity period 1 Activity end must lie within effectivity time 2 Activity start must lie within effectivity time 3 Do Not Take Validity Period Into Account

BJ9

1

BK9

3

BJ10

DEFINITION You can use the synchronization behavior to override synchronization of overlapping activities - as specified in a multi-activity or multi-mix resource - in this activity. USE If you do not make an entry, the synchronization behavior of the resource is used. This is the default behavior, which is identical to APO 2.0. If you override the synchronization behavior, overlapping with synchronized activities is not permitted for this activity. EXAMPLE You want to discharge a product at different, overlapping times from a container resource. You can do so by overriding the resource's synchronization behavior for the filling orders in question. In this way, the orders are neither synchronized nor scheduled without overlap.

BK10

use You use this field to restrict the possible dates and times (depending on the start or end date and time of the activity) for which an order can be scheduled or rescheduled. The following options are available: An order can only be scheduled or rescheduled to cause the specified activity dates and times to be within the order validity period. An order can be scheduled for any dates and times; the validity period is not considered. The system defines the validity period of an order when exploding the production process model (PPM). The system takes into account the validity periods of the order's products and components when determining the validity period for the order. dependencies You use the scheduling strategy in the strategy profile to define whether or not the system is to take into account the validity periods of orders when scheduling or rescheduling.

activity_text



char/ 60/ char/ 4/

BL4

MEANING Transfer parameter for language-dependent activity texts. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity Langu LanguIso To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

BL9

60

BM9

4

BL11


operation_number_extension activity langu langu_iso

Extension of Operation number (R/3) Activity Number Language Key Language according to ISO 639bapi10003r3oprnumextension /sapapo/actnr langu laiso

char/ 8/ char/ 40/ lang/ 1/ char/ 2/

BP8


BN9

8

BO9

40

BP9

2

BQ9

2

BO10


BP10


activity_tdpp

text plan_number

Activity Description External Name of Plan in Production Process Model/sapapo/acttypetext /sapapo/ext_plannr

char/ 40/ char/ 60/

BS4

MEANING Transfer parameter for time-dependent parameters of activities. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity PlanningVersion DateValidTo HINTS If the time-dependent parameters are to be used for all planning versions, the vale of the "PlanningVersion" field must be initial/blank. To set scrap at 10%, for example, the "Scrap" field must be filled with the value "0.1000".

BR9

40

BS9

60

BR10

DEFINITION Enter a name for the activity .

BS11


operation_number operation_number_extension activity

Operation Number Extension of Operation number (R/3) Activity Number/sapapo/cdps_operation_number bapi10003r3oprnumextension /sapapo/actnr


BT9

4

BU9

8

BV9

40

BV10


planning_version date_valid_to use_scrap_flg

Planning Version Validity period end Indicator Whether Maintained Scrap Should be Used/sapapo/vrsioex /sapapo/datet /sapapo/flag_scrap

char/ 10/ dec/ 15/ 0 char/ 1/

BY6

X TRUE FALSE

BW9

10

BX9

19

BY9

1

BW10


BY10

DEFINITION This indicator specifies whether the maintained scrap/yield should be used at the point of explosion. If the indicator is not set, the scrap from the routing activity is used. EXAMPLE The scrap for a routing activity: 5 per cent The following values with the corresponding maintained indicator are time and/or version dependent: Date to: Indicator Scrap 01.01.2000 X 6 01.02.2000 0 (blank) 01.03.2000 X 4 so the following values are used: Date to: Scrap 01.01.2000 6 01.02.2000 5 01.03.2000 4

activity_relation

scrap plan_number_pre operation_number_pre

Scrap Factor External Name of Plan in Production Process Model Operation Number/sapapo/scrap /sapapo/ext_plannr /sapapo/cdps_operation_number

dec/ 5/ 4 char/ 60/ char/ 4/

CA4

MEANING Transfer parameter for activity relationships. RANGE Key fields: PlanNumberPre OperationNumberPre OperationNumberPreExtn ActivityPre PlanNumberSucc OperationNumberSucc OperationNumberSuccExtn ActivitySucc ReferenceType HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used. Special Features The "MinTimeDeviation", "MaxTimeDeviation", and "AvrTimeDeviation" fields must always be transferred in the unit of measurement 'second'.

BZ9

6

CA9

60

CB9

4

operation_number_pre_extn activity_pre

Extension of Operation number (R/3) Activity Numberbapi10003r3oprnumextension /sapapo/actnr

char/ 8/ char/ 40/

CC9

8

CD9

40

CD10


plan_number_succ operation_number_succ


char/ 60/ char/ 4/

CE9

60

CF9

4

operation_number_succ_extn activity_succ

Extension of Operation number (R/3) Activity Numberbapi10003r3oprnumextension /sapapo/actnr

char/ 8/ char/ 40/

CG9

8

CH9

40

CH10


reference_type min_time_deviation max_time_deviation

Constraint Ref. Type (for Example Start-Start,...) for LC Minimum Interval Maximum interval/sapapo/om_constr_rel_type /sapapo/min /sapapo/max

int4/ 10/ quan/ 9/ 0 quan/ 9/ 0

CI6

0 Start-Start Relationship 1 Start-End Relationship 2 End-Start Relationship 3 End-End Relationship

CJ8

Reference Table: BAPI10003ACTREL Reference Field: UOM

CK8


CI9

1

CJ9

11

CK9

11

CI10

DEFINITION Reference type which indicates the relationship between the predecessor and successor activity on which the minimum or maximum interval of two activities is based.

CJ10

DEFINITION Indicates the minimum time difference between two activities linked by a relationship. USE Minimum intervals can be considered in scheduling or optimization in Productions Planning and Detailed Scheduling. When defining a minimum interval, you must Set the indicator Enter a value Choose a unit of measurement DEPENDENCIES You use the reference type to define the activity dates (start or end dates) to which the minimum interval refers. You define the unit of measurement for the minimum and maximum interval under unit of measurement. If you do not assign a value to the minimum interval, the default value of 0 is assigned.

CK10

DEFINITION The greatest interval allowed between two activities, which are linked via a relationship. use Maximum intervals can be considered in Production Planning and Detailed Scheduling during scheduling or optimization. To define the maximum interval, you must Set the indicator Enter a value Choose a unit of measurement dependencies You use the reference type to define the activity dates (start or end dates) to which the maximum interval refers. You define the unit of measurement for the minimum and maximum interval under unit of measurement.

min_deviation_flg max_deviation_flg resource_network_flg

Use Process-Related Minimum Interval Use Maximum Interval Resource Network/sapapo/fmin /sapapo/fmax /sapapo/frnf


CL6

X Minimum interval ready for input Minimum interval not ready for input

CM6

X Maximum interval ready for input Maximum interval not ready for input

CN6

X Resource network No resource network

CL9

1

CM9

1

CN9

1

CL10

use If you set this indicator, the Process-Related Minimum Interval field becomes ready to accept user input and you can specify an interval.

CM10

use If you set this indicator, the maximum interval field is activated and you can enter a maximum interval.

CN10

DEFINITION Using the resource network, you can link the modes of two activities that belong to different operations. Using the mode, you can save alternative resources for an operation in the production process model. By linking modes, the active mode of a prior activity (A1) influences the selection of a mode of a subsequent activity (A2). Both activities, A1 and A2, belong to different operations. The resource network checks the compatibility of the main resources of A1 and A2.

uom uom_iso material_flow_flg

Unit of Measure ISO code for unit of measurement Material Flow Along Relationship/sapapo/unit /sapapo/isocd_unit /sapapo/matflow

unit/ 3/ char/ 3/ char/ 1/

CQ6

X Material flow along relationship No material flow along relationship

CO8


CP8

Valuetable: T006I

CO9

3

CP9

3

CQ9

1

CQ10

DEFINITION Specifies whether or not there is a material flow between the activities linked by the relationship, that is, whether the material that is processed in the first activity is further processed in the second activity. USE You use this indicator to control how the system calculates the scrap from linked activities and the necessary input amount for the activities. If you set this indicator, the system cumulates the scrap from the linked activities. Example An operation consists of two consecutive processing activities. The first activity produces 20% scrap, the second activity 10%. The indicator is set, that is, the first activity passes on the material to the second activity. If the second activity is to produce a yield of 90, it needs an input quantity of 100 (10% scrap of 100 is 10). So that the first activity can deliver a yield of 100 to the second activity, it needs an input quantity of 125 (20% scrap of 125 is 25). If you do not set the indicator, the system calculates the scrap and the input quantities separately for each activity. Example An operation consists of two consecutive processing activities. The first activity produces 20% scrap, the second activity 10%. The indicator is not set, in other words the first activity does not pass on any material to the second activity. So that the first activity can produce a yield of 100, it must process 120. So that the second activity can produce a yield of 100, it must process 110.

mode_rel_type constr_subtype cover

Mode Linkage Type Reference Subtype Continuous Load of the Resources/sapapo/mode_rel_type /sapapo/constr_subtype /sapapo/cover

int1/ 3/ int1/ 3/ char/ 1/

CR6

0 Without resource restriction 2 Identical primary resource 3 Identical mode number

CS6

0 Standard 2 Use of resource time buffers

CT6

X TRUE FALSE

CR9

10

CS9

10

CT9

1

CR10

DEFINITION Indicates whether a mode linkage exists between two related activities. USE You use mode linkage if two related activities must be linked for optimization or explosion. The following options for mode linkage exist: Linkage of modes with identical names The modes of the activities must have identical names for linkage. The activities must also have the same number of modes. Linkage of modes according to primary resource The modes of two activities that are assigned to the same primary resource are linked. In this case, the names of the modes are unimportant. EXAMPLE Linkage of modes with identical names Activity,,1,,2 Mode,,abc,,abc The modes with identical names are linked for activities 1 and 2. Linkage of modes according to primary resource Activity,,1,,2 Mode,,abc,,def Primary resource,,123,,123 Modes with identical primary resources are linked. DEPENDENCIES In exceptional cases, the mode linkage can be violated during planning. You can be informed of these situations in the Alert Monitor by means of dynamic alerts. To activate this option you must first select the following alerts in the alert profile on the PP/DS tab page: Mode Linkage Violated Within an Order (under Constraint Alerts Within Order) Mode Linkage Violated Between Orders (under Constraint Alerts Cross-Order)

CS10

use In this field you can determine if the system should use the time buffer of the primary resource when planning this relationship. note Note that a time buffer between the setup activity and the processing activity of an operation is often not meaningful. dependencies You can determine if the system should use a time buffer when planning in the Detailed scheduling strategy.

CT10

DEFINITION Used in optimization or explosion to prevent a resource being occupied by activities of other orders in the period between two activities in a relationship (locked activity chain). USE A resource should be constantly used by two activities in an order. DEPENDENCIES This indicator is automatically set and cannot be changed, when a relationship is between two activities in the same operation that use the same primary resource.

avr_time_deviation avr_deviation_flg

Average Interval for Infinite Scheduling Use of Planning-Related Minimum Interval/sapapo/avrshift /sapapo/favr

quan/ 9/ 0 char/ 1/

CU8


CU9

11

CV9

1

CV10

use If you set this indicator, the planning-related minimum interval field is ready for input and you can specify a planning-related minimum interval.

scheduled_by_predecessor scheduled_by_successor

Scheduled Relationship Scheduled Relationship/sapapo/termby /sapapo/termby

char/ 1/ char/ 1/

CW6

X TRUE FALSE

CX6

X TRUE FALSE

CW9

1

CX9

1

mode



char/ 60/ char/ 4/

CY4

MEANING Transfer parameter for modes . RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity ModeNumber HINTS Note that the default value for the "MaxShortBreak" field is "9990000". This means that the field is set to this default value if it is not filled. When the plan is read using the "GetList" method, the default value is converted again to "0". To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

CY9

60

CZ9

4

CY11


operation_number_extension activity mode_number resource

Extension of Operation number (R/3) Activity Number Mode Number Resource Namebapi10003r3oprnumextension /sapapo/actnr /sapapo/om_modus /sapapo/cres_name


DA9

8

DB9

40

DC9

5

DD9

40

DB10


DC10

DEFINITION Modes are used to assign alternative primary resources to activities. DEPENDENCIES You can use the resource selection that is subordinate to the mode to also assign secondary resources to an activity.

DD10

DEFINITION Indicates the name of a resource.

DD11


uom uom_iso duration_var

Unit of Measure ISO code for unit of measurement Activity Duration (Variable)/sapapo/unit /sapapo/isocd_unit /sapapo/dur1


DE8


DF8

Valuetable: T006I

DG8

Reference Table: BAPI10003MODE Reference Field: UOM

DE9

3

DF9

3

DG9

17

DG10

DEFINITION Indicates the duration of the activity, which is dependent on the lot size of the material to be produced.

duration_fix penalty_var tdpp_flg

Duration of an Activity (Fixed) Single-Level Costs (Variable) Time-Dependent Parameters Maintained/sapapo/dur2 /sapapo/cost1 /sapapo/tipp

quan/ 13/ 3 int4/ 10/ char/ 1/

DJ6

X TRUE FALSE

DH8


DH9

17

DI9

10

DJ9

1

DH10

DEFINITION Indicates the duration of the activity, which is independent of the lot size of the material to be produced.

DI10


DJ10


production_in_shift max_short_break mode_priority

Production Within a Shift Maximum Duration of a "Short" Break Priority for Selection of a Mode/sapapo/ppm_prod_in_shift /sapapo/om_max_short_break /sapapo/ppm_mode_prio

char/ 1/ int4/ 10/ char/ 1/

DK6

X TRUE FALSE

DM6

A Priority A B Priority B C Priority C D Priority D E Priority E F Priority F G Priority G H Priority H I Priority I 0 Priority J 1 Priority K 2 Priority L 3 Priority M 4 Priority N 5 Priority O M Manual selection only

DK9

1

DL9

10

DM9

1

DK10

DEFINITION Indicates that the activity must be carried out within a shift.

DL10

DEFINITION Variable with data element /SAPAPO/MAX_SHORT_BREAK that defines the maximum length of a break for each mode so that the relevant mode can be interrupted by this break. This period must be specified in seconds. If a mode cannot be interrupted, the variable with data element /SAPAPO/MAX_SHORT_BREAK must be set to zero. Example: A mode can only be interrupted by "short" breaks, for example, a lunch break lasting one hour. The mode must not, however, be interrupted by a weekend. The relevant variable must then have the value 3600.

DM10

DEFINITION Modes describe the alternative resources at which an activity can be executed. Frequently, these alternatives may not be used with the same priority. Example: Often, an expensive machine should be used first so that an investment is worthwhile. You assign priority 'A' for the corresponding mode. Example: Specific resources may only be used for production in exceptional cases because they are intended, for example, for training or testing. These resources should only be used manually in the planning table. Choose priority 'M' for the corresponding mode.

duration_incrementation slot_start_grid break_not_allowed

Increment for Activity Duration Control of activity start Break not Allowed/sapapo/dur3 /sapapo/slot_start_grid /sapapo/break_allowed

quan/ 13/ 3 int1/ 3/ char/ 1/

DO6

0 Standard 1 Activity starts at beginning of shift

DP6

X Yes No

DN8


DN9

17

DO9

1

DP9

1

DN10

use When you enter an increment, the system rounds the activity duration calculated from the fixed and variable duration up to the next value that can be divided evenly by this increment. You can therefore model an activity duration with this increment that increases in steps (that is, a step function). example The work feed for a machine can hold up to 100 workpieces simultaneously. The processing operation takes 4 minutes, regardless of whether 1 piece or 100 pieces are loaded in the machine. The machine must therefore be refilled in order to process a lot of 170 pieces; for example, once with 100 pieces and once with 70 pieces. Therefore, to process this lot it takes 2 times 4 minutes. To process a lot of 240 pieces, it takes 3 times 4 minutes, and so on. The activity duration is therefore a step function. In order to model the behaviour of the activity, you enter the following data: Data for the activity duration Field ,,Value Unit of measure ,,MIN Increment ,,4 Variable duration*,,0,04 * Based on a base quantity of 1 piece The system determines the rounded activity duration for scheduling as follows: Activity duration calculated from the variable duration,, ,, Rounded activity duration Up to 4 minutes,,=> ,,4 minutes Up to 8 minutes,,=> ,,8 minutes Up to 12 minutes,,=> ,,12 minutes ...,,...,,

DO10

DEFINITION Defines the start of an activity.

DP10

DEFINITION Specifies that a mode may not be interrupted by a break. DEPENDENCIES Under exceptional circumstances, activities that may not be interrupted are nevertheless interrupted during scheduling and rescheduling. You can choose to be alerted to these situations by means of a dynamic alert in the Alert Monitor. To make this setting choose the alert Non-interruptible activity activity is interrupted by a break in the alert profile on the PP/DS tab page under Alerts for Activities of a Resource.

mode_tdpp



char/ 60/ char/ 4/

DQ4

MEANING Transfer parameter for time-dependent parameters of modes. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity ModeNumber PlanningVersion DateValidTo HINTS If the time-dependent parameters are to be used for all planning versions, the value of the "PlanningVersion" field must be inital/blank. To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used. Special Features The "DurationVar" and "DurationFix" fields must always be transferred in the unit of measurement 'second'.

DQ9

60

DR9

4

DQ11


operation_number_extension activity mode_number planning_version

Extension of Operation number (R/3) Activity Number Mode Number Planning Versionbapi10003r3oprnumextension /sapapo/actnr /sapapo/om_modus /sapapo/vrsioex


DS9

8

DT9

40

DU9

5

DV9

10

DT10


DU10


DV10


date_valid_to use_dur_var_flg display_uom_var

Validity period end Indicator for Use of Variable Parameter Unit of Measure/sapapo/datet /sapapo/flag_var /sapapo/unit

dec/ 15/ 0 char/ 1/ unit/ 3/

DX6

X TRUE FALSE

DY8


DW9

19

DX9

1

DY9

3

DX10

DEFINITION This indicator specifies if the maintained variable parameters should be used for an explosion date. If the indicator has not been set, the parameter value from the plan is used. EXAMPLE The values from the planning parameters are used: Variable Fixed Costs 5 2 25 The following values are maintained as time-dependent and version-dependent with the following indicators: Date to: Indicator Variable Indicator fixed Indicator Costs 01.01.2000 X 6 X 2 X 20 01.02.2000 0 (blank) X 3 X 20 01.03.2000 X 4 4 the following values are used: Date to: Variable Fixed Costs 01.01.2000 6 2 20 01.02.2000 5 3 20 01.03.2000 4 2 25

display_uom_var_iso duration_var use_dur_fix_flg

ISO code for unit of measurement Activity Duration (Variable) Indicator for Use of Fixed Parameter/sapapo/isocd_unit /sapapo/dur1 /sapapo/flag_fix

char/ 3/ quan/ 13/ 3 char/ 1/

EB6

X TRUE FALSE

DZ8

Valuetable: T006I

EA8

Reference Table: /SAPAPO/TDPP Reference Field: P1_MEINS

DZ9

3

EA9

17

EB9

1

EA10

DEFINITION Indicates the duration of the activity, which is dependent on the lot size of the material to be produced.

EB10

DEFINITION This indicator specifies if the maintained fixed parameter value should be used for an explosion date. If the indicator has not been filled, the value of the fixed parameter from the routing is used. EXAMPLE The values of the routing parameter are: Firstly, the system attempts to determine a time-dependent maintained value during the explosion. If this is not possible, the standard value is taken from the plan. The values of the routing parameter are: variable fixed costs 5 2 25 The following values with the corresponding maintained indicator are time and/or version dependent: Date to: Indicator Variable Indicator Fixed Indicator Costs 01.01.2000 X 6 X 2 X 20 01.02.2000 0 (blank) X 3 X 20 01.03.2000 X 4 4 so the following values are used: Date to: variable fixed costs 01.01.2000 6 2 20 01.02.2000 5 3 20 01.03.2000 4 2 25

display_uom_fix display_uom_fix_iso duration_fix

Unit of Measure ISO code for unit of measurement Duration of an Activity (Fixed)/sapapo/unit /sapapo/isocd_unit /sapapo/dur2


EC8


ED8

Valuetable: T006I

EE8

Reference Table: /SAPAPO/TDPP Reference Field: P2_MEINS

EC9

3

ED9

3

EE9

17

EE10

DEFINITION Indicates the duration of the activity, which is independent of the lot size of the material to be produced.

use_penalty_flg penalty

Indicator for using penalty parameters Single-Level Costs (Variable)/sapapo/flag_pen /sapapo/cost1

char/ 1/ int4/ 10/

EF6

X TRUE FALSE

EF9

1

EG9

10

EF10

DEFINITION This indicator specifies if the maintained costs should be used for an explosion date. If the indicator has not been filled, the costs from the plan are used. EXAMPLE The values of the routing parameters are: variable fixed costs 5 2 25 The following values with the corresponding maintained indicators maintained are time and/or version dependent: Date to: Indicator variable Indicator fixed Indicator Costs 01.01.2000 X 6 X 2 X 20 01.02.2000 0 (blank) X 3 X 20 01.03.2000 X 4 4 so the following values are used: Date to: variable fixed costs 01.01.2000 6 2 20 01.02.2000 5 3 20 01.03.2000 4 2 25

EG10


capacity_req



char/ 60/ char/ 4/

EH4

MEANING Transfer parameter for resource comsumption. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity ModeNumber Resource Location Loctype HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

EH9

60

EI9

4

EH11





EJ9

8

EK9

40

EL9

5

EM9

40

EK10


EL10


EM10


EM11


res_consump_var res_consump_fix

Continuous Resource Consumption (Variable) Continuous Resource Consumption (Fixed)/sapapo/cap1 /sapapo/cap2

quan/ 13/ 3 quan/ 13/ 3

EN8

Reference Table: BAPI10003REQCAP Reference Field: RES_CONSUMP_UOM

EO8

Reference Table: BAPI10003REQCAP Reference Field: RES_CONSUMP_UOM

EN9

17

EO9

17

EN10

DEFINITION Specifies the capacity consumption of a resource depending on a certain lot size. USE You have the following options for using the various resource categories: Resource,,Time-contin. consumption,,,,Bucket consumption Single-Activity,,,, Multi-Activity,, X Bucket,, ,,,,X Single-Mixed,, ,,,,X Multi-Mixed,, X,,,,X note Only the multi-activity resources have several capacities. Therefore, they also have a time-continuous consumption.

EO10

DEFINITION Specifies the capacity consumption of a resource irrespective of the lot size. If you work with a single resource, the fixed time-continuous consumption is always 1, since only one single resource exists that can only be used as a whole. Example An oven with only one baking tray. Consumption is lot-size-independent (thus fixed) and the resource cannot be subdivided. If you now work with a multi-resource (oven with several baking trays) you can define the distribution to the number of Kapazitäten of the of the resources (in our case, the number of baking trays). USE The resource types can be used as follows: Resource,,Time-Cont. Consumption,,,,Bucket Consumption Single-Activity,,,, Multi-Activity,, X Bucket,,,,,,,,,,X Single-Mixed,,,,,,,,,,X Multi-Mixed,, X,, Note Only the multi-mixed resources have several capacities. Therefore, they have a time-continuous consumption.

res_consump_uom res_consump_uom_iso res_calendar_flg

Unit of Measure ISO code for unit of measurement Calendar Resource/sapapo/unit /sapapo/isocd_unit /sapapo/cale


ER6

X Yes No

EP8


EQ8

Valuetable: T006I

EP9

3

EQ9

3

ER9

1

ER10

DEFINITION Specifies that the resource entered is the calendar resource of the mode.

tdpp_flg bucket_consump_var

Time-Dependent Parameters Maintained Bucket Resource Consumption (Variable)/sapapo/tipp /sapapo/bcap1

char/ 1/ quan/ 13/ 3

ES6

X TRUE FALSE

ET8

Reference Table: BAPI10003REQCAP Reference Field: BUCKET_CONSUMP_UOM

ES9

1

ET9

17

ES10


ET10

DEFINITION Specifies the capacity consumption of a resource depending on a certain lot size. USE You can use the different resource types in the following ways: Resource,,Time-continuous consumption,,,,Bucket consumption Single-activity,,,, Multiactivity,, X Bucket,, ,,,,X Single-mixed,, ,,,,X Multimixed,, X,,,,X note Only the multiresources have several capacities. Therefore, they also have a time-continuous consumption.

bucket_consump_fix bucket_consump_uom bucket_consump_uom_iso

Bucket Resource Consumption (Firmed) Unit of Measure ISO code for unit of measurement/sapapo/bcap2 /sapapo/unit /sapapo/isocd_unit


EU8

Reference Table: BAPI10003REQCAP Reference Field: BUCKET_CONSUMP_UOM

EV8


EW8

Valuetable: T006I

EU9

17

EV9

3

EW9

3

EU10

DEFINITION Specifies the capacity consumption of a resource, independently of the lot size. USE You can use the different resource categories in the following ways: Resource,,Time-continuous consumption,,,,Bucket consumption Single-activity,,,, Multiactivity,, X Bucket,, ,,,,X Single-mixed,, ,,,,X Multimixed,, X,,,,X note Only the multiresources have several capacities. Therefore, they also have a time-continuous consumption.

capacity_req_tdpp



char/ 60/ char/ 4/

EX4

MEANING Transfer parameter for time-dependent parameters of resource consumption. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity ModeNumber Resource Location Loctype PlanningVersion DateValidTo HINTS A time-dependent override can be made single activity resources. If the time-dependent parameters are to be used for all planning versions, the "PlanningVersion" field must be initial/blank. To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

EX9

60

EY9

4

EX11





EZ9

8

FA9

40

FB9

5

FC9

40

FA10


FB10


FC10


FC11


planning_version date_valid_to res_cons_var_flg

Planning Version Validity period end Indicator for Use of Variable Parameter/sapapo/vrsioex /sapapo/datet /sapapo/flag_var

char/ 10/ dec/ 15/ 0 char/ 1/

FF6

X TRUE FALSE

FD9

10

FE9

19

FF9

1

FD10


FF10


res_cons_var res_cons_var_uom res_cons_var_uom_iso

Continuous Resource Consumption (Variable) Unit of Measure ISO code for unit of measurement/sapapo/cap1 /sapapo/unit /sapapo/isocd_unit


FG8

Reference Table: BAPI10003TDPPREQCAP Reference Field: RES_CONS_VAR_UOM

FH8


FI8

Valuetable: T006I

FG9

17

FH9

3

FI9

3

FG10


res_cons_fix_flg res_cons_fix res_cons_fix_uom

Indicator for Use of Fixed Parameter Continuous Resource Consumption (Fixed) Unit of Measure/sapapo/flag_fix /sapapo/cap2 /sapapo/unit


FJ6

X TRUE FALSE

FK8

Reference Table: BAPI10003TDPPREQCAP Reference Field: RES_CONS_FIX_UOM

FL8


FJ9

1

FK9

17

FL9

3

FJ10


FK10


res_cons_fix_uom_iso bucket_cons_var_flg

ISO code for unit of measurement Indicator for Use of Variable Parameter/sapapo/isocd_unit /sapapo/flag_var

char/ 3/ char/ 1/

FN6

X TRUE FALSE

FM8

Valuetable: T006I

FM9

3

FN9

1

FN10


bucket_cons_var bucket_cons_var_uom

Continuous Resource Consumption (Variable) Unit of Measure/sapapo/cap1 /sapapo/unit


FO8

Reference Table: BAPI10003TDPPREQCAP Reference Field: BUCKET_CONS_VAR_UOM

FP8


FO9

17

FP9

3

FO10


bucket_cons_var_uom_iso bucket_cons_fix_flg

ISO code for unit of measurement Indicator for Use of Fixed Parameter/sapapo/isocd_unit /sapapo/flag_fix

char/ 3/ char/ 1/

FR6

X TRUE FALSE

FQ8

Valuetable: T006I

FQ9

3

FR9

1

FR10


bucket_cons_fix bucket_cons_fix_uom bucket_cons_fix_uom_iso

Continuous Resource Consumption (Fixed) Unit of Measure ISO code for unit of measurement/sapapo/cap2 /sapapo/unit /sapapo/isocd_unit


FS8

Reference Table: BAPI10003TDPPREQCAP Reference Field: BUCKET_CONS_FIX_UOM

FT8


FU8

Valuetable: T006I

FS9

17

FT9

3

FU9

3

FS10


logical_component



char/ 60/ char/ 4/

FV4

MEANING Transfer parameter for logical components.. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity LogComponent HINTS SNP plans and DP bills of material do not usually have a logical component. However, a logical component with the name of the material component must always be specified automatically for each material component. For this, the "CpDateTo" field in the "LogicalComponent" parameter must be filled with the value from the "DateTo" field in the "CompProduct" parameter. The "CpDateTo" field can be ignored for PP/DS plans. To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used. HINTS Special Features The "IoOffset" field must always be transferred in the unit of measurement 'second'.

FV9

60

FW9

4

FV11


operation_number_extension activity log_component io_indicator

Extension of Operation number (R/3) Activity Number Logical Component Input/Output Indicatorbapi10003r3oprnumextension /sapapo/actnr /sapapo/logcomp /sapapo/ioind


GA6

O Output: produced quantity I Input: Quantity taken out

FX9

8

FY9

40

FZ9

40

GA9

1

FY10


FZ10


GA10

DEFINITION Indicates whether the material in an operation is an input product or an output product (whether the product is consumed or produced in the operation). USE DEPENDENCIES EXAMPLE

consumption_mode relation_io_offset

Type of Material Consumption During Activity Starting Point for Offset/sapapo/om_matco /sapapo/offco

char/ 1/ char/ 1/

GB6

S Consumption at start of activity E Consumption at end of activity C Continual Consumption

GC6

S Offset refers to activity start E Offset refers to activity end

GB9

1

GC9

1

GB10

DEFINITION Specifies the time of production or use of a material. USE You can use the consumption type C (continous consumption) if materials flow continuously into production. This is the case, for example, at a bottle filling plant. Instead of creating an individual order with material consumption for each bottle, you can create an order for 1000 bottles that are then filled one after another. The same is true for repetitive manufacturing where large lots of a material are to be produced over several periods, for example, 1000 pieces in five days. Here the total quantity of 1000 pieces is not manufactured on the last day, but instead 200 pieces are produced each day. In the same way, the material does not need to be staged on the first day of prduction, but is distributed continously over the five days. The only change needed to be made to the settings in the production process model (PPM) is to set the indicator for the consumption type to C (continuous consumption). DEPENDENCIES EXAMPLE

GC10

DEFINITION Defines the starting time of an activity for the offset. The temporal offset specifies the timeframe that should be added to or subtracted from the start or end time of the activity in order to determine the time at which material consumption occurs. USE Use the input help to configure whether the end time of the offset should be the start or end of the activity. DEPENDENCIES EXAMPLE

io_offset io_offset_uom

Temporal Offset for Material Consumption Unit for Temporal Offset of Material Consumption/sapapo/iooff /sapapo/moffunit

quan/ 9/ 0 unit/ 3/

GD8

Reference Table: BAPI10003COMP Reference Field: IO_OFFSET_UOM

GE8


GD9

11

GE9

3

GD10

DEFINITION Specifies the temporal offset, that is, the timeframe that is added to or subtracted from the start or end time of the activity in order to determine the time at which material consumption occurs. USE Specify a value for the timeframe. This value can be either positive or negative. DEPENDENCIES EXAMPLE

GE10

DEFINITION Specifies a unit for the offset. USE Choose a unit in which the offset should be specified using the input help. DEPENDENCIES EXAMPLE

io_offset_uom_iso io_duration io_duration_uom

ISO code for unit of measurement Material Consumption Duration Material Consumption Duration Unit/sapapo/isocd_unit /sapapo/iodur /sapapo/mdurunit


GF8

Valuetable: T006I

GG8

Reference Table: BAPI10003COMP Reference Field: IO_DURATION_UOM

GH8


GF9

3

GG9

17

GH9

3

GG10

DEFINITION Material consumption can occur abruptly or over a certain period. You define the duration of the material consumption in this column of the table. USE Specify a value for the duration of the material consumption. DEPENDENCIES EXAMPLE

GH10

DEFINITION Defines a time unit for the duration of material consumption. USE Choose a time unit using the input help. DEPENDENCIES EXAMPLE

io_duration_uom_iso cp_date_to

ISO code for unit of measurement Validity period end/sapapo/isocd_unit /sapapo/datet

char/ 3/ dec/ 15/ 0

GI8

Valuetable: T006I

GI9

3

GJ9

19

comp_product



char/ 60/ char/ 4/

GK4

MEANING Transfer parameter for product components. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity LogComponent ProductAlt DateTo HINTS To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

GK9

60

GL9

4

GK11


operation_number_extension activity log_component product_alt

Extension of Operation number (R/3) Activity Number Logical Component External Product Indicatorbapi10003r3oprnumextension /sapapo/actnr /sapapo/logcomp /sapapo/ext_matnr


GP8


GM9

8

GN9

40

GO9

40

GP9

40

GN10


GO10


GP10


date_to date_from prod_consump_var prod_consump_fix

Validity period end Validity per. start Material Consumption (Variable) Material Consumption (Fixed)/sapapo/datet /sapapo/datef /sapapo/par1 /sapapo/par2

dec/ 15/ 0 dec/ 15/ 0 quan/ 13/ 3 quan/ 13/ 3

GS8

Reference Table: BAPI10003COMPALT Reference Field: PROD_CONSUMP_UOM

GT8

Reference Table: BAPI10003COMPALT Reference Field: PROD_CONSUMP_UOM

GQ9

19

GR9

19

GS9

17

GT9

17

GS10

DEFINITION Describes a variable material quantity that is required according to the lot size of a product. USE DEPENDENCIES EXAMPLE

GT10

DEFINITION Describes a fixed material quantity, which is required regardless of the lot size of a product.

penalty_var alt_prod_strategy ranking_order

Single-Level Costs (Variable) Alternative items strategy Ranking order/sapapo/cost1 /sapapo/alpst /sapapo/alprf

int4/ 10/ char/ 1/ numc/ 2/

GV6

1 Manual maintenance/by usage probability 2 100% check

GU9

10

GV9

1

GW9

2

GU10


percent_use_alt_strategy storage_location

Usage Probability for Alternative Strategy in % Sublocation/sapapo/uprob /sapapo/subloc

dec/ 3/ 0 char/ 4/

GY8

Valuetable: /SAPAPO/SUBLOC1

GX9

3

GY9

4

GY10

DEFINITION USE Sublocations subdivide a location into smaller units. A storage location from SAP R/3 is mapped in SAP APO as a sublocation.

tdpp_flg avert_product_explosion prod_consump_uom

Time-Dependent Parameters Maintained Prevent Product Explosion Unit of Measure/sapapo/tipp /sapapo/aexpl /sapapo/unit

char/ 1/ char/ 1/ unit/ 3/

GZ6

X TRUE FALSE

HB8


GZ9

1

HA9

1

HB9

3

GZ10


HA10

DEFINITION USE If you set this indicator, the system does not create any planned orders for this component when the plan is exploded. The system must cover dependent requirements with existing in-house production orders or external procurement orders. This indicator is only relevant to Capable-To-Match (CTM). DEPENDENCIES EXAMPLE

comp_product_tdpp

prod_consump_uom_iso plan_number

ISO code for unit of measurement External Name of Plan in Production Process Model/sapapo/isocd_unit /sapapo/ext_plannr

char/ 3/ char/ 60/

HD4

MEANING Transfer parameter for time-dependent parameters of product components. RANGE Key fields: PlanNumber OperationNumber OperationNumberExtension Activity LogComponent ProductAlt PlanningVersion DateValidTo HINTS If the time-dependent parameters are to be used for all planning versions, the "PlanningVersion" field must be initial/blank. To be able to use ISO codes, they must be assigned an SAP code in Customizing for units of measure. If both SAP code and ISO code are specified, the SAP code will be used.

HC8

Valuetable: T006I

HC9

3

HD9

60

HD11


operation_number operation_number_extension activity

Operation Number Extension of Operation number (R/3) Activity Number/sapapo/cdps_operation_number bapi10003r3oprnumextension /sapapo/actnr


HE9

4

HF9

8

HG9

40

HG10


log_component product_alt planning_version date_valid_to

Logical Component External Product Indicator Planning Version Validity period end/sapapo/logcomp /sapapo/ext_matnr /sapapo/vrsioex /sapapo/datet

char/ 40/ char/ 40/ char/ 10/ dec/ 15/ 0

HI8


HH9

40

HI9

40

HJ9

10

HK9

19

HH10


HI10


HJ10


use_prod_consump_var_flg prod_consump_var prod_consump_var_uom

Indicator for Use of Variable Parameter Material Consumption (Variable) Unit of Measure/sapapo/flag_var /sapapo/par1 /sapapo/unit


HL6

X TRUE FALSE

HM8

Reference Table: BAPI10003TDPPCOMPALT Reference Field: PROD_CONSUMP_VAR_UOM

HN8


HL9

1

HM9

17

HN9

3

HL10


HM10

DEFINITION Describes a variable material quantity that is required according to the lot size of a product. USE DEPENDENCIES EXAMPLE

prod_consump_var_uom_iso use_prod_consump_fix_flg prod_consump_fix

ISO code for unit of measurement Indicator for Use of Fixed Parameter Material Consumption (Fixed)/sapapo/isocd_unit /sapapo/flag_fix /sapapo/par2

char/ 3/ char/ 1/ quan/ 13/ 3

HP6

X TRUE FALSE

HO8

Valuetable: T006I

HQ8

Reference Table: BAPI10003TDPPCOMPALT Reference Field: PROD_CONSUMP_FIX_UOM

HO9

3

HP9

1

HQ9

17

HP10


HQ10

DEFINITION Describes a fixed material quantity, which is required regardless of the lot size of a product.

prod_consump_fix_uom prod_consump_fix_uom_iso use_penalty_flg

Unit of Measure ISO code for unit of measurement Indicator for using penalty parameters/sapapo/unit /sapapo/isocd_unit /sapapo/flag_pen


HT6

X TRUE FALSE

HR8


HS8

Valuetable: T006I

HR9

3

HS9

3

HT9

1

HT10

DEFINITION This indicator specifies if the maintained costs should be used for an explosion date. If the indicator has not been filled, the costs from the plan are used. EXAMPLE The values of the routing parameters are: variable fixed costs 5 2 25 The following values with the corresponding maintained indicators maintained are time and/or version dependent: Date to: Indicator variable Indicator fixed Indicator Costs 01.01.2000 X 6 X 2 X 20 01.02.2000 0 (blank) X 3 X 20 01.03.2000 X 4 4 so the following values are used: Date to: variable fixed costs 01.01.2000 6 2 20 01.02.2000 5 3 20 01.03.2000 4 2 25

ppm_model

penalty cp_date_to plan_number

Single-Level Costs (Variable) Validity period end External Name of Plan in Production Process Model/sapapo/cost1 /sapapo/datet /sapapo/ext_plannr

int4/ 10/ dec/ 15/ 0 char/ 60/

HW4

MEANING Transfer parameter for model assignments. If this parameter is empty, all PPMs specified are automatically added to the active model. If you do not want this default behavior, you have to set the "LV_NO_ACT_MODEL_ASSIGNMENT" parameter in user exit "EXIT_SAPL10003_001" to "X". As a result, no more model assignments are made and the PPM is created independently of a model. If a model assignment was made for a PPM, automatic model assignment never takes place. If the "RemoveFlag" indicator is set, the PPM specified is removed from the model. For this, there is no check for whether the PPM is still being used in this model. RANGE Key fields: PlanNumber PpmNumber Model

HU9

10

HV9

19

HW9

60

HU10


HW11


ppm_number model

Production Process Model: External Number Model Name in Supply Chain Network/sapapo/ext_ppmnr /sapapo/c_modelid

char/ 60/ char/ 22/

HY8


HX9

60

HY9

22

HY10


remove_flag

Select an Option (Yes = 'X', No = ' ')bapiyesno

char/ 1/

HZ6

No X Yes

HZ9

1

apo loader file document

Documents