Showing posts with label SAP Support Portal. Show all posts
Showing posts with label SAP Support Portal. Show all posts

Tuesday, 19 January 2016

Consumption Based Planning Process in SAP MM

The below SAP Tutorials help to know the consumption based planning procedures in detail. These are used in areas without in-house production and/or in production plants for planning both B- and C-parts and operating supplies. The consumption based planning Includes Recorder Point Planning, Forecast based Planning, and Time Phased Planning,we can discuss below in detail.

Reorder Point Planning

http://www.technosap.com/sap-tutorials/consumption-based-planning-process-in-sap-mm/

In the reorder point planning procedure, the system compares available warehouse stock with the reorder level. If available stock falls below the reorder level, an order proposal is generated. The reorder level (also known as the reorder point) is made up of the sum of the safety stock plus the expected average material consumption within the replenishment lead time. Therefore, when determining the reorder level, you must take safety stock, previous consumption values or future requirements and the replenishment lead time into account.

Safety stock must be set at a level which covers both excess material consumption within the replenishment lead time and the additional requirements which may occur during delivery delays. You must, therefore, take previous consumption or future requirements, and the vendor’s delivery timeliness or that of production into account when determining the safety stock level.

Forecast Based Planning

Like reorder point planning, forecast-based planning operates using historical values and forecast values as future requirements are determined via the integrated forecasting program. However, in contrast to reorder point planning, these values then form the basis of the planning run in forecast-based planning.

The forecast, which calculates future requirements using historical data, is carried out at regular intervals. This offers the advantage that requirements, which are automatically determined, are continually adapted to suit current consumption needs. If, during the current period, material has already been withdrawn from stock, then the forecast requirement is reduced by the quantity of material that was withdrawn. This mean that the quantity of the forecast requirement that has already been used is not included in the planning run again.

You can specify the period split for the forecast (daily, weekly, monthly or per accounting period) and the number of periods to be included in the forecast individually for each material. It is possible; however, that the forecast period split is not specific enough for planning purposes. Therefore, for each material, you can determine that the MRP forecast requirement values should be divided according to a finer period split. You can also determine how many forecast periods are to be taken into account during requirements planning.

For a monthly forecast, the requirements date would be set on the first workday of the month because, for planning, it is assumed that the total requirement must be available at the beginning of the period. You can then divide this monthly requirement into either daily or weekly requirements.

The requirements quantities forecast by the system are used in the planning run to carry out the net requirements calculation. During this calculation, every period is checked to make sure that the forecast requirements are covered either by available warehouse stock, by planned receipts from purchasing or by production. If the requirements forecast by the system are not met by these above mentioned possibilities, then an order proposal is generated.

Time Phased Planning


If a vendor always delivers a material on a particular day of the week, it makes sense to plan this material according to the same cycle in which it is delivered, but displaced by the delivery time. This is possible with the time-phased planning procedure. If a particular material is to be planned using this procedure, you must set the MRP type for time-phased planning and you must enter the planning cycle in the material master record. You enter the planning cycle in the form of a planning calendar in the Planning cycle field. You must also define a planned delivery time and the Lot-for-lot order quantity as the lot-size key.

You can also use the optimum lot-sizing procedures for time-phased planning. They are used here in the same way as in Reorder Point Planning. Materials that are planned using the time-phased planning technique are provided with an MPR date in the planning file. This date is set when creating a material master record and is re-set after each planning run. It represents the date on which the material is to be planned again and is calculated on the basis of the planning cycle entered in the material master record. For materials that are planned using the time-phased planning procedure, the two indicators, the total change indicator and the net change planning indicator are irrelevant. Therefore, they are not set by the system even if changes that are relevant to the planning run are made.

By using this planning technique, you can set the system so that it only plans materials on specific pre-defined days. For example, if you assign the same planning cycle to all the materials of a particular vendor, the system will always plan these materials on the same day. The purchase requisitions that are created in the planning run to cover material shortages can be processed, per vendor, by the MRP controller in the SAP purchasing system.

If you use the SAP Merchandise Management System, the system proposes the planning cycle from the vendor sub-range when you create a material master record. The vendor sub-range contains all the goods of a particular vendor that, from a logistical view, can be planned similarly.

You can also enter an MRP date during the planning run, meaning that you can bring the planning run forward to an earlier date, if necessary. For example, if the planning run is set for Monday, you can bring it forward to Saturday instead

More Details: SAP online training, SAP Solution Manager, SAP training courses, SAP fico training.

Monday, 21 December 2015

Outline agreement in SAP

This post explains general background information on the “outline agreements” (which, outside the SAP System, may also be referred to as blanket, master, framework or umbrella agreements) that are used in the SAP MM Purchasing component. In basic Outline Agreement can be classified with 2 different types. Contract and Scheduling agreements.

Contract is nothing but where you can have contract with the vendor,and this might be predetermined quantity. For example whenever you need the material the you need to make PO reference to this contract and asking for the delivery of the material.

Scheduling agreement
is nothing but long term purchase agreement, where you can keep issuing the delivery schedules whenever there is change in requirement or predetermined time intervals. We can classify the delivery schedule on hour or daily or weekly or monthly basis.

An outline agreement is a longer-term arrangement with the vendor regarding the supply of materials or the performance of services according to predetermined terms and conditions. In MM Purchasing, such agreements are subdivided into “contracts”and “scheduling agreements.” Outline agreements may be subject to a release (approval or clearance) procedure.

To Create Contract following the below steps:

Path to create Contract:
Logistics => Materials Management => Purchasing => Outline Agreement => Contract => Create
Transcation Code: ME31L

http://www.technosap.com/

The Structure of an outline agreement

As in the case of other purchasing documents, an outline agreement consists of the following elements:

Document header:
  • It contains information specific to the entire agreement.
  • For example: the vendor information and header conditions are in the document header.

Items:

  • Items that contain the information specific to the material or service. For example:
  • Statistics on ordering activities for the item
  • Quantity or price of the item
  • Pricing conditions, such as quantity discounts and surcharges

Texts in outline agreements

You can create your own texts from scratch in an agreement or change a text that has been suggested by the system. There are two kinds of agreement text: header text and item text. The texts are further subdivided into text types, for example, shipping and delivery instructions. The text type determines the print sequence on the document printout.

Outline agreement is nothing but long term purchasing agreement with vendor in containing certain terms and conditions regarding the raw material that is supplied by the vendor. Outline agreement which is valid up to certain period of time with some predefined quantity or value.

More Details: SAP Help Portal, Sap Online Tutorials, SAP Online Training Tutorials, SAP Training Tutorials.

Friday, 18 December 2015

SAP ERP: Technosap

SAP ERP is enterprise resource planning software developed by the German company SAP SE. SAP ERP incorporates the key business functions of an organization. The latest version (SAP ERP 6.0) was made available in 2006. The most recent Enhancement Package (EHP7) for SAP ERP 6.0 was released in 2013.

http://www.technosap.com/

Business Processes included in SAP ERP include Operations (Sales & Distribution, Materials Management, Production Planning, Logistics Execution, and Quality Management), Financials (Financial Accounting, Management Accounting, Financial Supply Chain Management) and Human Capital Management (Payroll, e-Recruiting)

Development

SAP ERP was built based on the former SAP R/3 software. SAP R/3 through version 4.6c consisted of various applications on top of SAP Basis, SAP's set of middleware programs and tools. When SAP R/3 Enterprise was launched in 2002, all applications were built on top of the SAP Web Application Server. Extension sets were used to deliver new features and keep the core as stable as possible. The Web Application Server contained all the capabilities of SAP Basis.

As a result of marketing changes and changes in the industry, new versions of SAP have been released. The first edition of mySAP ERP was launched in 2003 and bundled previously separate products, including SAP R/3 Enterprise, SAP Strategic Enterprise Management (SEM) and extension sets. The SAP Web Application Server was wrapped into NetWeaver, which was also introduced in 2003.

A complete architecture change took place with the introduction of mySAP ERP edition in 2004. R/3 Enterprise was replaced with the introduction of ERP Central Component (SAP ECC). The SAP Business Warehouse, SAP Strategic Enterprise Management and Internet Transaction Server were also merged into SAP ECC, allowing users to run them under one instance. Architectural changes were also made to support an enterprise service architecture to transition customers to a services-oriented architecture.

ERP advantages and disadvantages

Advantage
  • Allows easier global integration (barriers of currency exchange rates, language, and culture can be bridged automatically)
  • Updates only need to be done once to be implemented company-wide
  • Provides real-time information, reducing the possibility of redundancy errors
  • May create a more efficient work environment for employees
  • Vendors have past knowledge and expertise on how to best build and implement a system
  • User interface is completely customizable allowing end users to dictate the operational structure of the product
Disadvantages
  • Locked into relationship by contract and manageability with vendor - a contract can hold a company to the vendor until it expires and it can be unprofitable to switch vendors if switching costs are too high
  • Inflexibility - vendor packages may not fit a company's business model well and customization can be expensive
  • Return on Investment may take too long to be profitable
  • Implementations have a risk of project failure 

Wednesday, 16 December 2015

SAP Purchasing info Records Types: Technosap

The purchasing info records is source of information for purchasing. It contains information on a specific material and a vendor supplying the material. For example, the vendor’s current pricing is stored in the info record. The purchasing info records referred to in abbreviated form as called Info record.

Types of SAP Purchasing info records, There are two types of info records available in sap

http://www.technosap.com/sap-training/sap-purchasing-info-records-types/

Info records with a material master record (e.g. for stock material), This type of info record represents the relationship between a material or service (for which a master record exists) and a vendor.

Info records without a material master record (e.g. for consumable materials), This type of info record represents the relationship between a material or service for which no master record exists and a vendor.

Sucontractor info records
A subcontractor info records contains ordering information for subcontract orders. For example, if you subcontract the assembly of a component, the subcontractor info record would include the vendor’s (subcontractor’s) price for assembling the component.

Pipeline info records
The pipeline info record contains information on a vendor’s commodity that is supplied through a pipeline (for example, oil or water) or via similar means (for example, electricity through the mains). The info record contains the vendor’s price for the consumption of such commodities by the buyer (“pipeline withdrawals”). You can store withdrawal/usage prices for different validity periods.

Structure of an info records
An info record contains general data and organizational data:

General data -Data that is valid for each purchasing organization or each plant (for example, origin data, reminder levels, and the order unit). Organizational data – Data such as prices and pricing conditions that you can store for the relevant purchasing organization or plant.

Texts in the info records
The info record contains the following text types: Info record memo.. An internal note that is adopted in the PO item. The info record memo is not printed out

PO text in info records
This text serves to describe the order item and corresponds to the PO text in the material master record. It is adopted in the PO item and included in the printout.

Short text
For material that has a material master record, the short text (short description) is copied directly from the material master record into the PO or the outline purchase agreement.

Purchasing info records stores information on the material and vendor supplying the material. For Example, vendors present price of particular material is stored in info record. Purchase info record can be maintained at plant level or other end its at purchasing organization level.

More Details: SAP Solution Manager, SAP training courses, SAP fico training.

Tuesday, 8 December 2015

HR Human Resource Transaction Codes - Technosap.com

SAP HR Transaction Codes
 

SAP HR (Human Resource) module enables each company to effectively manage the employee information in their organization. SAP HR is integrated with other SAP modules and external systems. SAP HR Tcodes (Transaction codes) are the short-cut codes that will help users to take in to directly to the desired screen. To execute the transaction RPDTRA00 to list all
HR Transactions.

The followings are some useful SAP HR Tcodes:

SAP HR Tcodes – Master Data

Transaction Code  Description


PA10 Personnel file
PA20 Display HR Master Data
PA30 Maintain HR Master Data
PA40 Personnel Events
PA41 Change Hiring Data
PA42 Fast Data Entry for Events
PRMP Travel Expenses : Feature TRVPA
PRMD Maintain HR Master Data
PRMF Travel Expenses : Feature TRVFD
PRML Set Country Grouping via Popup
PRMM Personnel Events
PRMO Travel Expenses : Feature TRVCO
PRMS Display HR Master Data
PRMT Update Match code
PS03 Info type Overview
PS04 Individual Maintenance of Info types

SAP HR Tcodes – Time Management

PA51 Display Time Data
PA53 Display Time Data
PA61 Maintain Time Data
PA62 List Entry of Additional Data
PA63 Maintain Time Data
PA71 Fast Entry of Time Data
PBAB Maintain Vacancy? assignments
PT01 Create Work Schedule
PT02 Change Work Schedule
PT03 Display Work Schedule
PA64 Calendar Entry
PA70 Fast Data Entry

SAP HR Tcodes – Payroll

PA03 Change Payroll control record
PC00 Run Payroll
PC10 Payroll menu USA
PE00 Starts Transactions PE01 PE02 PE03
PE01 Schemas
PE02 Calculation Rules
PE03 Features
PE04 Create functions and Operations
PE51 HR form editor
PRCA Payroll Calendar
SPRO IMG
SE16 Data Browser (Table Reports)
PRCT Current Settings
PRCU Printing checks USA
PRD1 Create DME
SM31 Maintain Table
SM12 Locked Secessions
TSTC Table Look up
PP03 PD Tables
PPOM Change Org Unit
PO13 Maintain Positions
PO03 Maintain Jobs

SAP HR Tcodes – Benefits
 
PA85 Benefits – Call RPLBEN11
PA86 Benefits – Call RPLBEN07
PA87 Benefits – Call RPLBEN09
PA89 COBRA Administration
PA97 Salary Administration – Matrix
PA90 Benefits Enrollment
PA91 Benefits – Forms
PA92 Benefits Tables – Maintain
PA93 Benefits Tables – Display
PA94 Benefits – Access Reporting Tree
PA95 Benefits IMG – Jump to Views
PA96 Benefits reporting
PA98 Salary Administration
PA99 Compensation Admin – rel. Changes
PACP HR-CH : Pension fund, interface

SAP HR Tcodes – General Reporting


PM00 Menu for HR Reports
PM01 Dialogs in HR – Create Custom info types
PRFO Standard Form
PSVT Dynamic Tools Menu
PAR1 Flexible Employee Data
PAR2 Employee List

SAP HR Tcodes – Organizational Management
 

PPOM Change org Unit
PO03 Maintain Jobs
P013 Maintain Position
PO10 Maintain Organizational Unit
PP01 Maintain Plan Data (menu-guided)
PP02 Maintain Plan Data (Open)
PP03 Maintain Plan Data (Event-guided)
PP05 Number Ranges
PP06 Number Ranges Maintenance HR Data
PP07 Tasks/Descriptions
PP69 Choose Text for Organizational Unit
PP90 Setup Organization
PP01 Change Cost Center Assignment
PP02 Display Cost Center Assignment
PP03 Change Reporting Structure
PP04 Display Reporting Structure
PP05 Change Object indicators (O/S)
PP06 Change Object indicators OS
PPOA Display Menu Interface (with dyn.)
PPOC Create Organizational Unit
PPOM Maintain Organizational Plan
PPOS Display Organizational Plan
PQ01 Events for Work Center
PQ02 Events for Training Program
PQ03 Events for Job
PQ04 Events for Business Event Type
PQ06 Local Events
PQ07 Resource Events
PQ08 Events for External Person
PQ09 Events for Business Event Group
PQ10 Events for Organizational Unit
PQ11 Events for Qualification
PQ12 Resource Type Events
PQ13 Events for Position
PQ14 Events for Task
PQ15 Events for Company
PSO5 PD : Administration Tool
PSOA Work Center Reporting
PSOC Job Reporting
PSOG Org Mgmt General Reporting
PSO1 Tools Integration PA-PD
PSOO Organizational Unit Reporting
PSOS Position Reporting
PSOT Task Reporting

SAP HR Tcodes – Recruitment
  
PB10 Initial Entry of applicant master data
PB20 Display applicant master data
PB30 Maintain applicant master data
PB40 Applicant events
PB50 Display applicant actions
PB60 Maintain Applicant Actions
PB80 Evaluate Vacancies
PBA0 Evaluate Advertisements
PBA1 Applicant Index
PBA2 List of applications
PBA3 Applicant vacancy assignment list
PBA4 Receipt of application
HRP1505 DB Table for Infotype 1505
HRP1506 DB Table for Infotype 1506
HRP1507 DB Table for Infotype 1507
HRP1518 DB Table for Infotype 1518
HRP1519 DB Table for Infotype 1519
HRP1520 DB Table for Infotype 1520
HRP1600 Database Table for Infotype 1600
HRP1601 Database Table for Infotype 1601
HRPAD21 Additional data PAD21
HRPAD22 Additional data PAD22
HRPAD23 Additional data PAD23
HRPAD25 Additional data PAD25
HRPAD27 Additional data PAD27
HRPAD31 Additional data PAD31
HRPAD44 PAD44 Additional Data
HRPAD47 PAD47 Additional Data
HRPAD48 Additional Data PAD48
HRPAD50 Additional Data PAD50
HRPAD51 Additional data PAD51
HRPAD53 Additional Data PAD53
HRPAD63 PAD63 Additional Data
HRPAD77 Additional data for PAD77
HRPADBLIST Additional Data Databases
HRPADD2 Additional Data PADD2
HRPADD3 Additional Data PADD3
HRPADIC Additional Data PADD2
HRPADNLIST Additional Data Number List
HRPADNN General Additional Data Table
HRPADP1 Additional Data PADP1
HRPADP2 Additional Data PADP2
HRPADPM Additional Data PADPM
HRPADTI PADTI Additional Data
HRPADUZ PADUZ Additional Data- RequirementsAssignment of Persons
HRPADXN Additional Data PADXN
HRPS_T012K For Decoupled Access to T012K (House Bank and Account)
HRPVAC List of vacant positions

More Details: SAP Help Portal, SAP Training Tutorials, SAP Online Training Tutorials, Sap Online Tutorials.