Basic Functions Flashcards
(95 cards)
1
Q
Material substitution reasons fields: Strategy
A
Determines whether the substitution is automatic, provides a pop up for selection, general material determination with selection, without ATP
2
Q
Sales doc and material determination procedure relationship
A
You assign material determination procedure to a sales doc type
3
Q
BOM Group
A
A way to include or exclude components that belong to a collection of BOM materials. You can add components to a BOM group so that all the BOM materials in the group get the component.
4
Q
Types of Transfer of Requirements
A
Individual requirements
Collective requirements
5
Q
Individual requirements
A
A TOR occurs for each sales document that is created.
Source document can be identified by looking in the availability overview of each requirement
6
Q
Collective requirements
A
Combine several document quantities on certain criteria
Can be done done daily or weekly.
The source documents cannot be identified directly but can be determined from the list of orders for the material
7
Q
Requirement type, item category, and MRP type
A
Assign Requirement type to item category and MRP type of material
8
Q
Material Determination
A
When a material is entered and it’s not available or being phased out, it can automatically be replaced by another material. Follows a condition technique based material.
9
Q
Material Determination Configuration
A
Create condition tables Create access sequences Create condition types Creation determination procedure Assign material determination procedure to sales document type Define substitution reason
10
Q
Checking group
A
Controls how requirements are transferred to MRP. More specifically, whether the system creates individual or collective requirements in sales and distribution processing.
Field is called “Availability check” in the sales view of Material Master
11
Q
Checking rule
A
What stock types are included in ATP and what kind inward and outward movements are included in ATP calculation
12
Q
4 moving parts of the Availability Check
A
Checking group
Checking rule
Schedule line category
Delivery item category
13
Q
3 ways to trigger availability check
A
Change the ordered quantity
Change the plant
Manual button
14
Q
ATP Quantity moves based on…
A
potential stock changes
15
Q
ATP Quantity
A
Current Stock + Inward movement (planned receipts) + Outward movement (planned issues)
16
Q
Inward movement
A
Planned orders (internal procured) and Purchase
17
Q
Outward movement
A
Sales orders (works like reservations) and Deliveries
18
Q
Listing/Exclusion
A
Utilizes the condition technique
19
Q
Availability check is done at the…
A
Schedule line category level
20
Q
Requirement is short term for…
A
Transfer Of Requirement (TOR)
21
Q
MRP
A
Material Requirement Planning
22
Q
Requirement synonym
A
Demand
23
Q
Key inputs of MRP
A
Current Sales/Demand and Historic sales
24
Q
Key outputs of MRP
A
Purchase Requisitions and thus Purchase Orders
Planned Orders and thus Production Orders
25
Transfer of Requirements
The transferring of the necessary production/procurement requirements of a sales order to MRP.
26
Copy Control Flows
```
QT -> OR
OR -> LF
LF -> F2
RE -> LR (delivery)
F2 -> S1
F2 -> LR (IL)
F2 -> CR
CR -> G2
F2 -> DR
DR -> L2
```
27
VT(Target)(Source)
Copy Control Configuration t-codes
28
Copy Control Requirement/Routine
The check on document copy control plausibility
29
Requirement/Routines
Checks which are defined by code determining whether a process is permitted
30
Data Transfer Routines
Copy Control Routines which carry specific data from source document to target
31
Routines for Standard SAP
001-600
32
Routines for Custom
601-999
33
VOFM
T-code for creating custom routines
34
Replenishment lead time
RLT, the time it takes to get the goods ready and available for the customer
35
Replenishment lead time calculation: Internal Procurement
Current date + production time + G/R processing time
36
Procurement Type field
This field exists in the Material Master in MRP 2 view
37
The fields for RLT are set in the...
Purchasing and MRP views of Material Master
38
Replenishment lead time calculation: Externally Procurement
Purchasing lead time + G/R processing time + Planned delivery time
39
Purchasing lead time
How long it takes to convert a purchasing requisition into a purchase order
40
G/R processing time
How long it takes for the warehouse employees to receive and store the goods in the warehouse
41
Partner functions available in..
```
Customer Master
Sales order header
Sales order item
Delivery
Billing header
Billing item
```
42
Partner function configuration field: Unique
Only 1 occurrence per partner function
43
Partner function configuration field: Type
The type of partner, customer, logical system, etc
44
Partner function determination configuration field: Not modifiable
Not modifiable, partner function can not be modified after creation
Mandatory,
45
Partner Determination Procedure Customer account group Assignment
Customer account group is assigned to the partner determination procedure
46
Partner function customer account group assignment
Assign the partner function with the customer account group
47
Partner determination procedure sales document
Sales document type is assigned to the partner determination procedure
This configuration has source and origin, source being the previous transaction, and origin being master data
48
Backwards scheduling
Calculating the relevant dates for a delivery based on the customer's requested delivery date
Default
49
Forward scheduling
Calculating the delivery date by starting with the material availability date
Used if backwards scheduling fails
50
Incompletion procedure can be activated in...
```
Sales document types
Item Categories
Schedule line categories
Partner functions
Sales activities
Delivery types
Delivery item categories
```
51
Transfer of requirement dependent upon...
Requirement type
Requirement class
Checking group
Schedule line category
52
Requirements class
All Global settings for the Availability check & Transfer of Requirement are done here
Control the MRP, Consumption of PIR with Customer Requirement & Whether Customer Requirement are Relevant to Planning or not
Used in SD Configuration of Availability Check & Transfer of Requirements
53
Requirements type
We can define different Requirement Types like sales order requirements, delivery requirements or individual customer requirements. Determines the planning strategy to be used for a particular requirement
Assigned to Requirement Class in configuration in order to carryout Availability check & Transfer of Requirement.
used in SD Configuration of Availability Check & Transfer of Requirements
54
Criteria needed for transfer of requirements to be carried out
```
Plant must be assigned to sales document line item
Schedule line category must be switched on for TOR
TOR must be switched on at requirements class level
Checking group must be defined and allocated to MM record in sales: General/Plant view
```
55
Consumption modes
Defines whether and in which direction on the time axis from the requirements date the consumption of customer requirements with planned independent requirements should occur.
56
Consumption mode options
```
No planning consumption
Backwards consumption only
Forwards consumption only
Backwards/forwards consumption
Forwards/backwards consumption
```
57
Requirements date
Date the sales order was created
58
Backwards consumption only
Starting from the requirements date, backwards consumption is carried out within the relevant consumption period
59
Forwards consumption only
Starting from the requirements date, forward consumption is carried out within the relevant consumption period
60
Backwards/forwards consumption
Starting from the requirements date, backwards consumption is performed first of all. Then, if no planned independent requirements can be allocated before the requirements date, forward consumption is performed. Both procedures are carried out for the relevant consumption period.
61
Forwards/backwards consumption
Starting from the requirements date, forward consumption is performed first of all. Then, if no independent requirements can be allocated after the requirements date, backwards consumption is performed. Both procedures are carried out for the relevant consumption period.
62
Planning materials
Used for planning purposes only. It is not actually produced, but is used to pass on the dependent requirements of the non-variable parts from the finished product
63
Requirement type Requirement class allocation
```
Requirement type is allocated to 1 requirement class
Requirement class can be allocated to many requirement types
```
64
Pre-defined search strategy for requirement type
Find requirements type using strategy group in MM
If strategy group not maintained, system will determine it using MRP group
If MRP group not defined, system uses material type
If no requirements type is found, system assumes a special rule and attempts to find a requirements type by the item cat and the MRP type
Final attempt to find a requirement type with the item category
System declares the transaction as not relevant for availability check or TOR
65
3 types of availability check
On the basis of the ATP quantities
Check against product allocation, allowing a predefined distribution quantity of products to customers
Takes place in the stand-alone APO planning system
66
Two type of standard checking groups
01 daily requirements
| 02 individual requirements
67
Copy control config: Copy item number
Used when you copy the entire previous document into a new document. The same header and item numbers you had will be copied.
68
Copy control config: Complete reference
Useful in copying legally approved quotations into a sales document. Restricts the user into copying the entire document as opposed to partially copying data.
69
Incompletion logs can be created for...
```
Sales doc header data
Sales doc item data
Sales doc schedule line data
Sales activity data
Partner data in sales docs, deliveries, and sales activities
Delivery header data
Delivery item data
```
70
You can assign incompletion procedure to...
```
Sales document types
Item categories
Schedule line categories
Partner functions
Sales activities
delivery types
delivery item types
```
71
Partner determination can be defined for...
```
Customer master
Sales doc header
Sales doc item
Delivery
Shipment
Billing doc header
Billing doc item
Sales activities (CAS)
```
72
Text Determination config
Choose text object
Text type
Define access sequence (not needed for customer master record text objects, customer master record is the highest level possible in text determination)
Create the text procedure
Assign the text type to the procedure
Assign the procedure to the account group
73
System accesses the forms of payment in the following sequence..
Payment card activated first (if a payment card is entered in the document)
Documentary payment guarantees are activated immediately
Export cred insurance is activated if a valid contract exists
74
Product hierarchy level maximum
9
75
Customer hierarchy can be defined for...
```
Sales doc header
Sales doc item
Delivery
Shipment
Billing header
Billing item
Sales activities (CAS)
```
76
Output determination activities...
```
Sales activities
Sales documents
Outbound Deliveries
Inbound deliveries
Handling units
Groups
Shipments
Billing Documents
```
77
Statuses that may be incomplete...
```
General
Delivery
Billing document
Price
Goods movement
Picking
Packing
```
78
Defining incompletion procedure
Select the incompletion group
| Select procedures
79
Partner determination configuration
Partner determination procedures have partner functions assigned within them
Partner determination procedures are assigned to customer account groups
You must assign newly created account groups to the list of account groups allowed to have partner determination procedures
Partner functions are assigned to account groups
80
Copy Control doc config: FPLA
A routine that checks that certain billing plan requirements have been met and then copies relevant billing plan data into the proceeding document
81
Copy Control doc config: Configuration
Used for the item category representing the main item of a configurable product.
Configurable product, a basic product that can be configured by the customer to their specific requirements ala a car
82
Copy Control doc config: reexplode structure/free goods
Used when you wish the system to redetermine the bill of materials in the sales document.
83
Copy Control doc config: positive/negative qty
Use for document flow if you have specified the completion indicator on an item category type
Determines how the value taken from the source document will affect the billing documents
84
Copy Control doc config: Copy quantity
forces the system to copy the quantity of the field best suited for the document type being referenced
85
Copy Control doc config: Copy item copy mode
Specifies how the material in a value contract item may be copied
86
Copy Control doc config: Copy product select.
Specifies whether the system automatically copies the results of product selection from a source sales document to a target sales document
87
Copy Control doc config: PricingExchRate type
determines which date to uses as the basis for the exchange rate
88
Copy Control doc config: Cumulate cost
Used to determine if the cost is to be rounded up from the sub-items to a main item
89
A material can be assigned to only one...
Division
90
Plant determination sequence
Customer-material info record
Customer Master record
Material Master
91
Data in a sales order is not re-determined after a change of the sold-to party
Sales office and sales group
| Availability and product allocation
92
The standard calculation rules provided by SAP for the free goods
The free goods quantity is the quantity that is calculated from the discount quantity
The document quantity is the quantity entered by the person who creates a sales order
93
Rescheduling is dictated by...
Customer delivery priority
| "Fixed order/date" field in order item level
94
Info that can be changed when you create an outbound delivery reference to a sales order
Delivery qty
Weight
Planned goods issue date
95
Transaction variant
You can change the layout of the screen. Transaction variants are actually made up of a series of screen variants. The field values and settings for each screen in the transaction variant are stored in a screen variant.
