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

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.

SAP SD Online Training Tutorials

Free SAP SD (Sales and Distribution) Training Tutorials

SAP SD ( Sales and Distribution ) Training tutorials by the real time functional consultant and experts . The SAP SD module handles all the processes starting from an Order to delivery. The main operations of this SAP SD module handle Customer Sales Orders processing, pricing, Picking, packing, Shipping, billing and risk management etc.

Sales and Distribution (SD) is one of the core and most-used modules of SAP R/3 products beside Financial (FI), Controlling (CO), Material Management (MM), and Production Planning (PP) modules. The Sales & Distribution (SD) module consists of various components also called sub-modules. Which are follow as below,

(SD-BF) Basic Functions and Master Data in SD Processing. (Also subdivided in several components as: Pricing, Output…etc)
(SD-BF-PR) Pricing and Conditions
(SD-BF-EC) Extra Charge
(SD-BF-CM) Availability Check and Requirements in Sales and Distribution Credit and Risk Management
(SD-BF-AS) Material Sorting
(SD-BF-OC) Output Determination
(SD-SLS) Sales
(SD-SLS-OA) Scheduling Agreements for Component Supplierssap sd training tutorials
(SD-SLS-OA) Customer Service Processing
(SD-FT) Foreign Trade/Customs
(SD-BIL) Billing
(SD-BIL-IV) Payment Card Processing
(CAS) Sales Support: Computer-Aided Selling
(SD-EDI) Electronic Data Interchange/IDoc Interface
(LE-SHP) Shipping
(LE-TRA) Transportation
(SD-IS-REP) Reports and Analyses

SAP SD (Sales and Distribution) module and with the sub module are

• Pre-sales activities, including Inquiry and Quotation creation.
• Sales Order processing, including Sales Order (SO)
• Shipping, including Outbound Delivery document creation.
• Billing, including Billing document and invoice creation.

Sales and Distribution (SD) is a module highly integrated with other SAP Modules as FI, CO, MM, PP & more. This can make SAP SD complex module, so as part of this Introduction we will also try to detail a normal sales process and how the activities integrate and are covered by this module.

Pre-sales activities: It starts when a customer or a prospect requests information by any source about a product or service offered by the company. This request is processed through SAP and the first integration we have is by the creation of an Inquiry Document or a Quotation Document. At this point of the process we still haven’t effectively made a sale that’s why it is considered as a presale activity.

Sales Order processing: Our quotation document previously created is send to our customer so they can make effective their purchase procedure. At this point they may want to negotiate payment terms, price, dates or any adjustments to the original document created by us.

As soon as we receive a Purchase Order (PO) from our Customer we create a Sales Order (SO) which makes reference to the previously created Quotation Document. Now scenario  is adjusted based on the business requirements. In some cases depending on the business Sales Orders (SO) can be made without a previously created quotation document as also in other scenario this can be a requirement.

Inventory Sourcing: The product requirement from the Sales Order at the required date needs to be available by one of the following options:

To fulfill the products requirement from an SO at the required date, we can obtain them by one of these options:

• Taking from Available stock at warehouse. At this point the SD module may trigger stock transfers between warehouses.
• Triggering a production order to produce the products in-house.
• Triggering a purchasing order to purchase the products from vendor.

Here is where the integration between Production Planning (PP) and Material Management (MM) starts.

Shipping: When the product we sold is available at the warehouse, the sales personnel can start shipping activities by creating an outbound delivery document (Delivery Order/DO). Now this Deliver Order (DO) can be created by referring to our original Sales Order (SO). This will trigger the preparation of the product by the personnel of the warehouse. If the Warehouse Management (WM) module is integrated, a Deliver Order (DO) can trigger a Transfer Order. When the products are ready to be sent, the warehouse personnel will post the Goods Issue (GI) transaction that refers to the DO. The GI transaction will reduce the inventory level of products and then the warehouse personnel sends the products to the customer by transportation mode that has been determined in Sales Order (SO) document.

Billing: This whole process will be managed before the delivery date specified in the Sales Order (SO) document. The finance department will generate a billing document and send an invoice form to the customer. The invoice will request the customer to pay the products we have sent at the price condition and terms of payment we have agreed in SO document.

SAP Sales and Distribution consists of all business processes required in selling, shipping the goods, and final billing of the item. This SAP SD module is closely integrated with other SAP Modules.

More Details: SAP Support Portal,SAP online training,SAP Solution Manager,SAP training courses.

How to Explain Output determination Procedure in SAP SD?

Output determination Transaction code : (NACE T-code)

Output is a form of media from a business to one of its business partners. The possible media forms are printouts, faxes, telexes, e-mails, and EDI. The output can be sent to any of the partners defined in the document. Outputs are usually in the form of order confirmations, delivery notes, invoices, and shipping notifications.



Output determination to maintain 8 activities

A. Sales Activities

B. Sales document’

C. Deliveries

D. Picking lists

E. Shipping units

F. Groups (type of collective processing_

G. Shipments

H. Billing Document

1. Maintain Condition Table

2. Access Sequence

3. Output Type

BA00-Order Confirmation

1. In condition type in general record assign the access sequence

2. Here one can do setting either access sequence should purpose from condition record or customer master records

3. One can set here business partner SP, BP, Ship to party etc. Screen :

Default values

4. Assign Output Types To Partner Functions

Specify a previously defined output type. Specify the allowed partner functions. Define an output medium (for example, printout, telefax, or mail).

5. Maintain Output Determination Procedure

6 Assign output Determination Procedure

Sales order confirmation

1. Maintain output types (Transaction: V/30 or Sales & Distribution -> Basic Functions -> Output -> Output determination -> Output proposal using the condition technique -> Maintain output determination for sales document -> Maintain output types)

1.1. Select and copy BA00 to ZA00

1.2. Access sequence 0003 (Sales org / customer). If one of these is not suitable then you need to maintain condition tables

1.3. Change Transm. Medium to 6 (EDI), partner function SP (Sold to), Time (4 = immediate)

1.4. Check access to conditions and check off multiple issuing

1.5. Save

2. Assign output determination procedure (Transaction V/47 or Sales & Distribution -> Basic Functions -> Output -> Output determination -> Output proposal using the condition technique -> Maintain output determination for sales document -> Assign output determination procedure)

2.1. Create a new entry for ZA00, medium 6, function SP and order confirmation.

3. Maintain output determination procedure (Transaction V/32 or Sales & Distribution -> Basic Functions -> Output -> Output determination -> Output proposal using the condition technique -> Maintain output determination for sales document -> Maintain output determination procedure)

3.1. Check Assign output determination procedures -> Allocate sales document header (Transaction V/43) for the Output procedure being used for order OR and BA00 and you’ll find that it is linked to V10000

3.2. Select V10000 (Transaction v/32) and choose control

3.3. Add a new step for your new output type. Eg. Step 40 (Next Step in sequence), Counter, Type = ZA00 and requirement 22 (Requirement tells when the output is required to be fulfilled. Ie. After order confirmation, after goods issue, …)

4. Create condition records (Menu path: Logistics –

> Sales & Distribution -> Master data. Output -> Sales document – Create)

4.1. If required select the appropriate key combination (in this case the Sales org / customer relationship)

4.2. Enter the customer number (QWM000 in this case) and enter. The rest of the values should be read in except the partner number.

4.3. Enter the required partner number (QWM000 in this case). This is the partner that will be EDI’d the data. It is usefull when you have multiple SAP customers that need to send messages to 1 partner. Eg. All the Wal-Marts send their invoices to 1 office. You would then have a list of customers, relating to each Wal-Mart, pointing to 1 Wal-Mart partner that will receive all the EDI docs.

Advance shipping notification

Similarly the output type was copied from LALE to ZALE and linked to partner QWM000

Based on when a delivery note is created (Transaction V/36)

Invoice

Similarly the output type was copied from RD00 to ZD00 and linked to partner QWM000

Based on when a delivery goods issue is posted. (Transaction V/42)

More Details: Learn SAP Online, SAP Support Portal, SAP online training.

Request For Quotation (RFQ)

What is request for quotation (RFQ) in sap?

The Request For Quotation (RFQ) is an invitation to a vendor to indicate his terms and conditions (in particular, his price) for the supply of a material or the provision of a service by submitting a quotation. As in the case of the purchase requisition, the RFQ identifies the material, quantity, and delivery date.

In addition, the RFQ contains information about the vendor to whom the request for quotation (RFQ) is sent (for example, the vendor’s name and address) and important dates for the RFQ (such as the closing date for applications, or pre-qualification date, and bid submission deadlines). RFQs can be subject to a release procedure.

Structure of an RFQ in SAP
The request for quotation is organized as other purchasing documents. The header contains general information about the RFQ, such as the vendor address. Each item identifies the individual materials for which a price is required from the vendor. One main difference between request for quotation (RFQs) and other purchasing document types is the fact that you cannot enter account assignments for RFQ items.

To Create RFQ in SAP use the Transaction code: ME41

What is a quotation in SAP?

The quotation contains the vendor’s pricing and conditions for providing the material or service stated in the RFQ. In SAP MM Purchasing, the request for quotation and quotation are the same document. You enter the vendor’s pricing and conditions in the original RFQ.

Then you can find the below points

• To use the price comparison list to help you determine the best quotation.
• To send rejection letters to the appropriate vendors.
• To store the pricing and terms of delivery for certain quotations in the info record for future reference.

Processing of request for quotation (RFQs) and Quotations.

• You do the following when processing sap request for quotation RFQs and quotations:
• You create an RFQ manually or by referencing a requisition.
• You specify which vendors will receive the request for quotation. A separate document is created for each addressee.
• You enter the prices and conditions from the vendor’s quotation into the request for quotation RFQ.
• You can monitor the status of the request for quotation and quotation as it is further processed (that is, following creation of a contract or purchase order).

More Details: Learn SAP Online, SAP Support Portal, SAP online training.

Material Ledger Closing in SAP Quick review

Movements for a material that is valuated with the material ledger are always carried out using the valuation price. If the price control indicator in the material master record is S, movements for the material are carried out with the standard price. If the price control indicator in the material master record is V, movements for the material are carried out with the periodic unit price.

When postings such as invoice receipts occur, the prices can differ from the valuation price. These differences are collected and totaled by the material ledger and taken into account during material ledger closing.

The Before Material Ledger Closing: The differences between the valuation price that occur when postings are made are collected the following categories:

GR/IR (goods receipt/invoice receipt): Differences between actual values and the valuation price that may occur due to invoice receipts are collected here. Differences can occur between a goods receipt and an invoice receipt, because the invoice price is unknown at the time of goods receipt. The values from invoice receipts are posted to a GR/IR clearing account and the offsetting entry is made in the vendor account.

Value Variances: Differences between actual values and the valuation price that can occur due the to the following are collected as,

1. The Goods receipts for the production order
2. Transfer postings
3. Goods issues
4. The Initial entries of inventory data with a specified amount
5. Deliveries free of charge
6. Inward movements from consignment inventory to the company’s own stock
7. Purchase order-related goods receipts

Values from goods receipts are posted to a GR/IR clearing account; the offsetting entry takes place in the material inventory account. If the the order price differs from the valuation price in the goods receipt, the system posts an offsetting entry to the material stock account and the price difference account (transaction key PRD). Such differences are totaled in the material ledger and indicated as to be closed. With goods receipts that are not based on a purchase order item, price difference are posted directly to the price difference accounts.

Posting to a Prior Period: Variances are collected here when a posting is made to the previous period using a valuation price other than the one in the current period.

At Material Ledger Closing: At material ledger closing, the system takes the differences arising in the above categories into account, depending on the price control of the material. If you carry out material ledger closing for a single material (without saving), you can display which postings the material ledger would make and with what amounts if you were to save the material ledger closing at this time

Materials with S price control (standard price): The system calculates for each material, the balance on the GR/IR clearing account and posts this amount to a price difference account (transaction key PRY). Differences that were collected in the Value variances category were posted to various price difference accounts before material ledger closing. These postings are not changed.

Differences that were collected in the Posting to a prior period category were posted to the revaluation account before material ledger closing. These postings are not changed. The new periodic unit price is calculated for statistical information.

Materials with V price control (periodic unit price): The system calculates the balance on the GR/IR clearing account and posts this amount to the material stock account in proportion to the current inventory quantity. The portion of the balances with which the material inventory cannot be debited are posted to a price difference account (transaction key PRY). Differences that were collected in the Value variances category were posted to various price difference accounts before material ledger closing. These postings are offset in total against a separate price difference account at material ledger closing (transaction key PRY).

The system calculates the balance and posts this amount to the material stock account in proportion to the current inventory quantity. The portion of the balances with which the material inventory cannot be debited are posted to a price difference account (transaction key PRY)

Differences that were collected in the Posting to a prior period category were posted to the revaluation account before material ledger closing. The system calculates the balance on this account and posts this amount to the material stock account in proportion to the current inventory quantity.

The portion of the balances with which the material inventory cannot be debited are posted to a price difference account (transaction key PRY). The postings to the material stock account result in a new periodic unit price for the material, found by dividing the inventory value by the inventory quantity.

More Details: Learn SAP Online, SAP Support Portal, SAP online training, SAP Solution Manager.

SAP SD Tables list Overview

SAP Training Tutorials gives to know more on the SAP SD tables which using frequently in SAP SD sales and distribution module. The list of important SP SD tables as below,

General Tables

• KNA1 : General Data
• KNB1 : Customer Master – Co. Code Data (payment
• method, reconciliation acct)
• KNB4 : Customer Payment History
• KNB5 : Customer Master – Dunning info
• KNBK : Customer Master Bank Data
• KNKA : Customer Master Credit Mgmt.
• KNVP : Partner Function key
• KNVD : Output type
• KNVS : Customer Master Ship Data
• KNKK : Customer Master Credit Control Area Data (creditlimits)
• KNVV : Sales Area Data (terms, order probability)
• KNVI : Customer Master Tax Indicator
• KLPA : Customer/Vendor Link
• VBUK : Header Status and Administrative Data

SAP Sales Order Document Tables

• VBAK : Sales Document – Header Data
• VBKD : Sales Document – Business Data
• VBUP : Item Status
• VBAP : Sales Document – Item Data
• LIPS : Delivery Document item data, includes referencing PO
• LIKP : Delivery Document Header data
• VBPA : Partners
• VBFA : Document Flow
• VBEP : Sales Document Schedule Line
• VBBE : Sales Requirements: Individual Records
• VBRK : Billing Document Header
• VBRP : Billing Document Item
• VEKP : Shipping Unit Item (Content)
• VEPO : Shipping Unit Header

SAP Shipping & Delivery Document Tables

• LIKP : SD Document: Delivery Header Data
• LIPS : SD document: Delivery: Item data
• VEPO : Packing: Handling Unit Item (Contents)
• VEKP : Handling Unit – Header Table
• VTTP : Shipment Item
• VTTK: Shipment Header
• VBLK : SD Document: Delivery Note Header

SAP Billing Document Tables

• VBRK : Billing Document: Header Data
• VBRP : Billing Document: Item Data
• VBSS : Collective Processing: Sales Documents
• VKDFS: SD Index: Billing Initiator
• NAST : Message Status
• VBSK : Collective Processing for a Sales Document Header
• VRPMA: SD Index: Billing Items per Material
• VRKPA : Sales Index: Bills by Partner Functions

SAP Material Master Data Tables

• MARA : General Material Data
• MAKT : Material Descriptions
• MARM : Units of Measure for Material
• STXH : STXD SAPscript text file header
• STXL : STXD SAPscript text file lines
• MARC : Plant Data for Material
• MVKE : Sales Data for Material
• T179 : Materials: Product Hierarchies
• MLAN : Tax Classification for Material

More Details: SAP Online Training Tutorials, SAP Training Tutorials, Learn SAP Online, SAP Support Portal.

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.