Tuesday, May 28, 2013
SAP official configuration guides Link
SAP BEST PRACTICES FOOD AND BEVERAGE PACKAGE - BUILDING
BLOCKS
Monday, May 20, 2013
Manufacturing Order Data Archiving
Requirements of Data Archiving
The main purpose of data archiving is to remove from the database application data that is no longer needed in day-to-day business, with the aim of using resources more efficiently. The following requirements must betaken into account when archiving data:
•Legal requirements: Some kinds of data must be archived so that they can be analyzed at any time in the future, for example data required by the tax authorities. These requirements are subject to the laws of the relevant country. SAP has developed the Data Retention Tool (DART)to enable the US Internal Revenue Service to analyze archived data. The tool includes functions for creating transparent files from archived data and to display this data.
•Technical requirements: From a technical point of view, the question is whether data can still be read long after it has been archived, independent of the hardware used at the time of archiving and the software release status. To guarantee this, SAP Data Archiving stores, together with the actual application data, additional information about the hardware that was used to write the data to the archive and what type of data structure was applied.
•Business requirements: From the business point of view, only those data objects that are no longer required in day-to-day operations may be removed from the database. Therefore, a logic check must be performed to ensure that only data objects belonging to completed business processes can be archived.The high level of integration between R/3 System applications means that the data objects are closely linked. Consequently, it is essential, during archiving, to check whether the removal of a specific data object from the database requires other objects to be archived at the same time.
SAP Note for Manufacturing Order Archiving
The main purpose of data archiving is to remove from the database application data that is no longer needed in day-to-day business, with the aim of using resources more efficiently. The following requirements must betaken into account when archiving data:
•Legal requirements: Some kinds of data must be archived so that they can be analyzed at any time in the future, for example data required by the tax authorities. These requirements are subject to the laws of the relevant country. SAP has developed the Data Retention Tool (DART)to enable the US Internal Revenue Service to analyze archived data. The tool includes functions for creating transparent files from archived data and to display this data.
•Technical requirements: From a technical point of view, the question is whether data can still be read long after it has been archived, independent of the hardware used at the time of archiving and the software release status. To guarantee this, SAP Data Archiving stores, together with the actual application data, additional information about the hardware that was used to write the data to the archive and what type of data structure was applied.
•Business requirements: From the business point of view, only those data objects that are no longer required in day-to-day operations may be removed from the database. Therefore, a logic check must be performed to ensure that only data objects belonging to completed business processes can be archived.The high level of integration between R/3 System applications means that the data objects are closely linked. Consequently, it is essential, during archiving, to check whether the removal of a specific data object from the database requires other objects to be archived at the same time.
SAP Note for Manufacturing Order Archiving
SAP PP tables
MAST - Material BOM
STKO - BOM Header
STPO - BOM Positions (detail)
MAPL - Assignment for Task Lists to Materials
PLKO - Routing Group Header
PLSO - Routing Group Sequence
PLPO - Routing Group Operations
AFKO - Production Order Header
AFPO -Production Order Position (details)
Related tables in MM area :
MAKT - Material Descriptions
MARA - General Material Data
MARC - Plant Data for Material
MARD - Storage Location Data for Material
MAST - Material to BOM Link
Sunday, May 19, 2013
Dead Stock Concept in MC50
MC50 looks at the stock level for a material over a period of time and identifies the lowest level that the material reached. That lowest level is the dead stock quantity as, in theory, that stock was not required. It works on the principle that in an ideal world scenario you would maintain zero stock sitting in the warehouse because you were able to plan such that every day you receive / produce the exact amount that you require to meet all customer requirements with no surplus.
An example would be that if you met all demand over a 3 month period and the stock level in that time never dropped below 100 then that would be the dead stock level as throughout the period you supposedly could have had 100 less stock and still met all requirements.
Dead stock is the part of your warehouse stock that has not been used for a certain period of time. In contrast to the safety stock (intended dead stock), the dead stock value allows you to identify materials with inefficient amounts of stock.
Generally a dead stock occurs if there is too much stock. This may be due to restrictions concerning minimum purchase quantities. Early purchasing and provisioning may lead to dead stock as well, which indicates maladjusted control parameters.
Production Planning Reports
Report Name
|
Transaction Code (SAP GUI)
|
Business Role (SAP NWBC)
|
Technical role name (SAP NWBC)
|
Production Order Information System
|
COOIS
|
Manufacturing
|
SAP_BPR_SHOPFLOORSPECIALIST-S
|
Missing Parts Info System
|
CO24
|
Production
Planner
|
SAP_BPR_P_
PRODUCTIONPLANNER_EX-S |
Capacity Planning
|
CM01
|
Strategic Planner
|
SAP_BPR_STRATEGICPLANNER-S
|
Long-Term Capacity Planning
|
CM38
|
Strategic Planner
|
SAP_BPR_STRATEGICPLANNER-S
|
Long-Term Planning: MRP List
|
MS05
|
Strategic Planner
|
SAP_BPR_STRATEGICPLANNER-S
|
Change Plan
|
MC82
|
Strategic Planner
|
SAP_BPR_STRATEGICPLANNER-S
|
Evaluation of Product Group Planning
|
MD47
|
Production
Planner
|
SAP_BPR_P_
PRODUCTIONPLANNER_EX-S |
Selection: Plan/Actual/Variance
|
S_ALR_87013532
|
Project Manager
|
SAP_BPR_PROJECTMANAGER-S
|
Costs/Revenues/
Expenditures/Receipts |
S_ALR_87013531
|
Project Manager
|
SAP_BPR_PROJECTMANAGER-S
|
Actual/Plan/
Variance Absolute/ Variance % |
S_ALR_87013543
|
Project Manager
|
SAP_BPR_PROJECTMANAGER-S
|
Order Progress Report
|
CO46
|
Production Planner
|
SAP_BPR_P_
PRODUCTIONPLANNER_EX-S |
Display Production Order Confirmation
|
CO14
|
Shop Floor Specialist
|
SAP_BPR_SHOPFLOORSPECIALIST-S
|
Sunday, May 12, 2013
What are the highest organizational units
What are the highest organizational units in SD, MM.PP,FI,CO?
SD: Sales Organizations.
MM: Plant
PP: Plant
FI: Company Code
CO: Controlling Area
SD: Sales Organizations.
MM: Plant
PP: Plant
FI: Company Code
CO: Controlling Area
Production Planning (PP) sub-modules
SAP Production Planning (SAP PP) is compromised of the following modules:
• Master Data - includes the material master, work centers, routings and bill of materials.
• SOP - Sales and Operations Planning (SOP) provides the ability to forecast sales and production plans based on historical, current and future data.
• DRP - Distribution Resource Planning allows companies the ability to plan the demand for distribution centers.
• Production Planning - includes material forecasting, demand management, long term planning and master production scheduling (MPS).
• MRP - Material Requirements Planning relies on demand and supply elements with the calculation parameters to calculate the net requirements from the planning run.
• Shop Floor Control - includes the processing of production orders, goods movements, confirmations and reporting tools for production.
• Capacity Planning - evaluates the capacity utilized based on the work centers available capacity to show capacity constraints.
• Repetitive Manufacturing - in repetitive manufacturing, the manufacturing process is usually simple in that the same products are produced over a long period of time. This module provides the transactions and business process for companies to run repetitive manufacturing in SAP.
• KANBAN - is a process of replenishment based on a pull system using KANBAN cards to generate the replenishment cycle.
• Product Cost Planning - is the process of evaluating all the time values and value of component materials to determine the product cost.
• Master Data - includes the material master, work centers, routings and bill of materials.
• SOP - Sales and Operations Planning (SOP) provides the ability to forecast sales and production plans based on historical, current and future data.
• DRP - Distribution Resource Planning allows companies the ability to plan the demand for distribution centers.
• Production Planning - includes material forecasting, demand management, long term planning and master production scheduling (MPS).
• MRP - Material Requirements Planning relies on demand and supply elements with the calculation parameters to calculate the net requirements from the planning run.
• Shop Floor Control - includes the processing of production orders, goods movements, confirmations and reporting tools for production.
• Capacity Planning - evaluates the capacity utilized based on the work centers available capacity to show capacity constraints.
• Repetitive Manufacturing - in repetitive manufacturing, the manufacturing process is usually simple in that the same products are produced over a long period of time. This module provides the transactions and business process for companies to run repetitive manufacturing in SAP.
• KANBAN - is a process of replenishment based on a pull system using KANBAN cards to generate the replenishment cycle.
• Product Cost Planning - is the process of evaluating all the time values and value of component materials to determine the product cost.
Monday, May 6, 2013
SAP Production /Process Order the following configuration is required
SAP Production /Process Order the following configuration is required:
a) Order type Definition settings
b) Order type Dependant parameters settings
c) Assigning a number range (external or internal) to the order type
d) Scheduling parameters for an Order type
e) Define Confirmation Parameters
f) Configure production scheduling profile
g) Default operation for the generation of operations
h) Default values for availability checks
a) Order type Definition settings
b) Order type Dependant parameters settings
c) Assigning a number range (external or internal) to the order type
d) Scheduling parameters for an Order type
e) Define Confirmation Parameters
f) Configure production scheduling profile
g) Default operation for the generation of operations
h) Default values for availability checks
Auto GR
Auto GR:
Ø
In the final operation of the routing, enter Control key with Auto
GR tick
Ø
In OPKP Production Scheduling profile tick Auto GR in The GR
screen.
Auto GI/ Backflush
Auto GI/ Backflush:
Ø
In Material Master in MRP 2 views set the back flush indicator
Ø
In Work center in basic data view you have to tick the back flush
indicator. It will affect only material used in particular work center.
Ø
In Routing, Component allocation Screen you can set back flush
indicator. It will affect only in that routing.
Ø
In the customizing, in OPK4 tick the Goods movement all components
in the General valid setting.
Steps Involved in PP cycle
Steps Involved in PP cycle:
*Requirements
is flowing in any of the two ways or both, one from sales order( VA01), another
from
Planned independent requirement( MD61) or customer requirement( MD81).
*Check
whether the requirement is flowing correctly in Stock requirement list( MD04)
*Run a
MRP in Single material multilevel (MD02) if there is any Reorder point planning
material
run MRP
in Plant level ( MD01)
*Check
whether planned order is created for a header material and all dependent
material in Stock requirement list (MD04).
*Convert
the planned order into purchase requisition for external procurement material
(MD14 or MD15 or MD04), if it is in house production convert the planned order
in to production order in stock requirement list (MD04, CO40 for individual
conversion, CO41 for collective conversion, CO48 for partial conversion).
*Once
production order is created, release the order, allocate the capacity to work
center, availability check and check the cost and save it.
*Once the
order is created, dependent requirement is converted into reservation.
*Issue
the dependent material to MIGO,
*Confirm
the order using CO15, if you want to confirm operation wise , then confirm in
CO11N.
*Once the
confirmation is made, then goods receipt for the order is carried out
*Set TECO
in CO02 (change of production order)
*Month
end activity (Calculate the WIP in KKAX)
*Calculate
the Overhead in KKS2, variance calculation and settlement of order.
Subscribe to:
Comments (Atom)