Showing posts with label Functional. Show all posts
Showing posts with label Functional. Show all posts

Mar 27, 2014

Understanding infotype Time constraint

  •  Infotypes are information units in the Human Resources Management system. Groups of related data fields are bundled into infotypes.
  • Infotypes structure information, facilitate data entry and allow data to be saved for specific periods. Infotypes serve as templates for users to enter data. From a database point of view, infotypes provide a data structure and a set of coherent data records. 
  •  The infotypes Actions 0000,  Organizational Assignment 0001, Personal Data 0002, and Payroll Status 0003 are prerequisites for entering a personnel or applicant number.
  •  Save the infotypes at intervals to build up an infotype history. The system stores a validity period for each infotype record. Therefore, several data records usually exist for each infotype of an employee, and each record has a different validity period.
  •  You use a time constraint to determine how the data records of an infotype react to each other in terms of time.
  • Several infotypes have subtypes, which break down information further. For example, technically speaking, the address types for infotype Address 0006 represent the subtypes
  • Each infotype and subtype has a time constraint.
  •  Time constraint 1: Complete saving with no overlaps at any time, that is, one valid data record of the relevant infotype must exist during the duration of the employee's employment at the company.
  •  Time constraint 2: Incomplete saving without overlaps at any time, that is, of an infotype may exist at a given time. No more than one valid data record of the infotype can exist at any given time.
  • Time constraint 3: Incompleteness and overlaps permitted, that is, any number of valid data records of an infotype may exist at any given time.

Time Constraints A: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible. View V_T582B Infotypes which are Created Automatically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action. Infotypes with time constraint A may not be deleted.
Time Constraints B: Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible. Infotypes with time constraint B may be deleted.
Time Constraints T: The time constraint varies depending on the subtype.
For the Addresses infotype (0006), you can assign a different time constraint for each subtype. In this way, you can make sure that a main address always exists for the employee and you can also enter temporary residences, if necessary.
Time Constraints Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y  Time Constraint Reaction.

Jan 26, 2013

MM Process flow in SAP


MM Process flow:

The typical procurement cycle for a service or material consists of the following phases:

1. Determination of Requirements:

Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the order-point method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system.

2. Source Determination:

The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired.

3. Vendor Selection and Comparison of Quotations

The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically.

4. Purchase Order Processing

The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported.

5. Purchase Order Follow-Up

The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders.

6. Goods Receiving and Inventory Management

Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and underdeliveries of ordered goods.

7. Invoice Verification

The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment.

Common Tables used by SAP MM:
Below are few important Common Tables used in Materials Management Modules:
EINA Purchasing Info Record- General Data
EINE Purchasing Info Record- Purchasing Organization Data
MAKT Material Descriptions
MARA General Material Data
MARC Plant Data for Material
MARD Storage Location Data for Material
MAST Material to BOM Link
MBEW Material Valuation
MKPF Header- Material Document
MSEG Document Segment- Material
MVER Material Consumption
MVKE Sales Data for materials
RKPF Document Header- Reservation
T023 Mat. groups
T024 Purchasing Groups
T156 Movement Type
T157H Help Texts for Movement Types
MOFF Lists what views have not been created
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types

Transaction Codes:
RFQ to Vendor - ME41
Raising Quotation - ME47
Comparison of Price - ME49
Creation of PO - ME21N
Goods Receipt - MIGO
Invoice (Bill PAssing) - MIRO
Goods Issue - MB1A
Physical Inventory - MI01( Create doc)
MI04 (Enter Count)
MI07 (Post)

SD Process Flow in SAP

SD PROCESS FLOW:

1. Sales Inquiry.
2. Quotation.
3. Sales order.
4. Delivery/Shipping.
5. Billing.
6. Invoice.





How to change Transport request from Released to Modifiable

Step 1: Go to SE38 – Execute Program RDDIT076.  Step 2: Give your released requests number and execute again. Step 3: After executing, yo...