__
1.What is Report and the Purpose of Reports in real time ?
Report is displaying the application data in the required format. Technically speaking, a report is an executable program with three stage function:
DATAINPUT (Selection Screen)
DATA PROCESSING (SELECT Statements)
DATAOUTPUT. (Write, Skip, Uline, Vline etc to Output the Data).
Diagram: SAP Institutes Output
O
Database
Purpose : It helps to analyze the current situation and also for decision making. I.e to Decide the right Institute using the above Report.
Real time Report Scenarios :
i.e. to stop the Purchases from the Specific Vendors, the Purchasing Department need a report for Vendor Evaluation and to terminate the employees from the Organization ,the HR Department need one report with Employee Performance etc.
2.How to Skip <N> Lines on the Selection Screen ?
SELECTION-SCREEN SKIP <N>. Selection Screen (Input) Database Retrieval Logic Ratings ---1 E00---1 eMAX 2 I001 iMAX 3 R001 Reliance 4 E002 Epic 5 V001 Version IT
__
3.The Role of Dynamic Internal Table SCREEN in Screen MODIFY . And How to Modify the Screen/Selection Screen ?
The Purpose of Moifying the Screen is that certain field on the screen
• Appear only in certain conditions.
• Are in Change/Display mode according to user inputs.
• Becomes mandatory subject to specific inputs.
• Changes it’s format depending upon certain conditions.
Note:Every time the screen is displayed, it considers the attributes from The Dynamic Internal table SCREEN and Display it. So that to modify the Selection /Normal Screen it is enough to MODIFY the internal table SCREEN accordingly.
Note:The Processing Logic to MODIFY the SCREEN table Should be
Executed Under Event AT SELECTION-SCREEN OUTPUT for Selection Screen. PROCESS BEFORE OUTOUT for Normal Screen.
Modify the Screen
At the runtime, attributes for each screen field is stored in a system defined internal table with header line called as SCREEN TABLE. It contains name of field and its attributes. This table can be modified during the runtime.
__
FIELD NAME LENGTH DESCRIPTION
_____________ __________ ______________________
NAME 30 Name of screen field
GROUP1 3 Field belongs to field group1
GROUP2 3 Field-grp-2
GROUP3 3 Field -grp-3
GROUP4 3 Field -grp-4
ACTIVATE 1 Field is visible &
ready for Input
REQUIRED 1 Field input is mandatory
INPUT 1 Field ready for input
OUTPUT 1 Field for display only
INTENSIFIED 1 Field is highlighted
INVISIBLE 1 Field is suppressed
LENGTH 1 output length is reduced
DISPLAY 3D 1 Displayed with 3D frame
VALUE_HELP 1 Displayed with value help
Note : Go through the Example Program for better understand REPORT ZDEMO_MODIFY_SCREEN .
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001. "Source Of the File
PARAMETER : P_PRE(100) TYPE C , P_APP(100) TYPE C.
SELECTION-SCREEN END OF BLOCK B1.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-002. "Source Of the File
PARAMETER : R_PRE RADIOBUTTON GROUP G1 DEFAULT 'X' USER-COMMAND COM1,
R_APP RADIOBUTTON GROUP G1. SELECTION-SCREEN END OF BLOCK B2.
__ LOOP AT SCREEN. IF R_PRE = 'X' AND SCREEN-NAME = 'P_APP'. SCREEN-INPUT = 0. MODIFY SCREEN. ELSEIF R_APP = 'X' AND SCREEN-NAME = 'P_PRE'. SCREEN-INPUT = 0. MODIFY SCREEN. ENDIF. ENDLOOP. OutPut :
Select the Application Server Radiobutton and Notice the Result.
Input is enabled Only for the Presentation Server for the
__
4.How to Place the PUSH Buttons(Function Keys) On Application Tool Bar of the Selection Screen ?
Note : Go through the Below Program to Understand it in Detail. TABLES sscrfields.
data : it_t001 like table of t001.
data v_bukrs type bukrs value 'BUKRS'.
SELECTION-SCREEN BEGIN OF block B0 WITH frame title text-000. PARAMETERS: p_kunnr TYPE kunnr,
p_ktokd TYPE ktokd.
SELECTION-SCREEN end OF block B0.
SELECTION-SCREEN BEGIN OF block B1 WITH frame title text-001. PARAMETERS: p_lifnr TYPE lifnr,
p_ktokk TYPE ktokk.
Input is enabled Only for the Application Server for the
__ SELECTION-SCREEN end OF block B1. SELECTION-SCREEN: FUNCTION KEY 1, FUNCTION KEY 2.
SELECTION-SCREEN BEGIN OF SCREEN 500 . PARAMETER : NAME1 AS CHECKBOX,
ORT01 AS CHECKBOX, LAND1 AS CHECKBOX.
SELECTION-SCREEN END OF SCREEN 500. SELECTION-SCREEN BEGIN OF SCREEN 5000 . PARAMETER : NAME AS CHECKBOX,
p_sortl AS CHECKBOX, p_ort01 AS CHECKBOX, p_ort02 AS CHECKBOX, p_regio AS CHECKBOX.
SELECTION-SCREEN END OF SCREEN 5000. INITIALIZATION.
sscrfields-functxt_01 = 'Customer Data'. sscrfields-functxt_02 = 'Vendor Data'. AT SELECTION-SCREEN.
CASE sscrfields-ucomm. WHEN'FC01'.
CALL SELECTION-SCREEN 500 STARTING AT 10 10. WHEN 'FC02'.
CALL SELECTION-SCREEN 5000 STARTING AT 10 10. ENDCASE.
Output :
__
__
5.How to Place the PUSH buttons(Function Keys) On Selection Screen?
By using SELECTION-SCREEN PUSHBUTTON <(pos)(len)> <pushbutton name> USER-COMMAND <UCOM>.
6.Can We Place More than One Selection Screen Element in One Line , If Yes , How ?
YES.
SELECTION-SCREEN BEGIN OF LINE. {List Of PARAMETERs to be Included} SELECTION-SCREEN END OF LINE.
NOTE:When we group more than One Selection Screen element in the same line, the selection texts/Default Names are disappeared and so the same can be done through SELECTION-SCREEN 10(20) COMMENT <TEXT-0005>.
__
7.How to Validate the Selection Screen , and How important it is to Validate the Selection Screen ?
Note:Before we Leave the Input Screen , the input should be validated
Either to retrieve the Data from the Database or to update the database tables as the input data should be always VALID.
We Can Say , the Input is Valid Only when the corresponding Master Data table has at least one entry for the given Input V.
So Use SELECT UP TO 1 ROWS to read one record, if found valid else, display the User Friendly Information on the Selection Screen itself.
Note : Displaying the Information on the Selection Screen is Always through Messages.
The Messages Should be Called through the EVENTs.
AT SELECTION-SCREEN ON <Field> to Validate Single Field.
AT SELECTION-SCREEN is to Validate all the Selection Screen Elements. Message Calling :
MESSAGE E<nnn> (Message Class) WITH <value1> <Value2> …
8.What is the difference between SELECT SINGLE ' and SELECT UP TO 1 ROWS?
Note : Both retrieves Only One Record Always.
SELECT SINGLE SELECT UP TO 1 ROWS
Syntax SELECT <List Of Fields> into <WA> FROM <DBT> WHERE <Condition>.
SELECT <List Of Fields> into <WA> FROM <DBT> UP TO 1 ROWS
WHERE <Condition>. 1 It Reads the Exact Record It Reads the First Record
Found(May not be Exact)
2 The WHERE Condition Should
Include all the Primary Keys
The WHERE Condition Can have the Part of the
__
To Identify the record Uniquely. Primary Key. 3 Prefer this to read the Exact
Information. Prefer this to Validate Input as we are not Interested with the Exact Match.
Because a record is Valid if at least one record found. Note1 :
When we Don’t Pass all the Primary Keys in the SELECT SINGLE , it Acts as SELECT UP TO 1 ROWS, but doesn’t throw error.
Note 2 : If the Input is SELECT-OPTIONS We cannot expect SINGLE Record and where as we can expect UP TO 1 ROWS because it can be any record for the Input Range.
9.What is sequence of event triggered in report?
1) Initialization 2) At Selection-Screen 3) Start-of-Selection 4) Get 5) Get Late 6) End-of-Selection 7) Top-of-Page 8) Top-of-Page-During Line-Selection 9) End-of-Page 10) At Line Selection
__
11) At User Command
12) At PF (nn)
10.What are the system fields you have worked with? Explain?
1) SY-DBSYS - Central Database 2) SY-HOST - Server
3) SY-OPSYS - Operating System 4) SY-SAPRL - SAP Release 5) SY-SYSID - System Name
6) SY-LANGU - User Logon Language 7) SY-MANDT - Client
8) SY-UNAME - Logon User Name 9) SY-DATLO - Local Date 10) SY-DATUM - Server Date 11) SY-TIMLO - Local Time 12) SY-UZEIT - Server Time 13 SY-DYNNR - Screen Number 14) SY-REPID - Current ABAP program 15) SY-TCODE - Transaction Code 16) SY-ULINE - Horizontal Line
__ 17) SY-VLINE - Vertical Line
18) SY-INDEX - Number of current loop Pass 19) SY-TABIX - Current line of internal table 20) SY-DBCNT - Number of table entries processed 21) SY-SUBRC - Return Code
22) SY-UCOMM - Function Code 23) SY-LINCT - Page Length of list 24) SY-LINNO - Current Line
25) SY-PAGNO - Current Page Number 26) SY-LSIND - Index of List
27) SY-MSGID - Message Class 28) SY-MSGNO - Message Number 29) SY-MSGTY - Message Type
30) SY-SPONO - Spool number during printing
11.What are control level processing and events(Statements)in a loop?
Control level processing (Contol Break Statements):
Control level processing is allowed within a LOOP over an internal table. This means that you can divide sequences of entries into groups based on the contents of certain fields.
__
Internal tables are divided into groups according to the sequence of the fields in the line structure. The first column defines the highest control level and so on. The control level hierarchy must be known when you create the internal table.
The control levels are formed by sorting the internal table in the sequence of its structure, that is, by the first field first, then by the second field, and so on. Tables in which the table key occurs at the start of the table are particularly suitable for control level processing.
The AT statement introduces a statement block that you end with the ENDAT statement.
AT <Level>. {Statement Block} ENDAT.
The Effect of the following control level changes: <level> Meaning
AT FIRST First line of the internal table AT LAST Last line of the internal table
AT NEW <f> Beginning of a group of lines with the same contents in the field <f> and in the fields left of <f>
AT END Of
<f> End of a group of lines with the same contents in the field <f> and in the fields left of <f> Within the loop, you must order the AT-ENDAT statement blocks according to the
hierarchy of the control levels. If the internal table has the columns <f1>, <f 2>, ...., and
if it is sorted by these columns, you must program the loop as follows:
LOOP AT <itab>. AT FIRST. ... ENDAT. AT NEW <f1>. ... ENDAT. AT NEW <f2 >. ... ENDAT. ...
__ ... AT END OF <f2>. ... ENDAT. AT END OF <f1>. ... ENDAT. AT LAST. .... ENDAT. ENDLOOP.
You do not have to use all control level statements. But you must place the used ones in the above sequence. You should not use control level statements in loops where the line selection is restricted by WHERE or FROM and TO. Neither should the table be modified during the loop.
If you are working with a work area <wa>, it does not contain the current line in the AT... ENDAT statement block. All character fields to the right of the current group key are filled with asterisks (*). All other fields to the right of the current group key contain their initial value.
Within an AT...ENDAT block, you can calculate the contents of the numeric fields of the corresponding control level using the SUM statement.
SUM.
You can only use this statement within a LOOP. If you use SUM in an AT - ENDAT block, the system calculates totals for the numeric fields of all lines in the current line group and writes them to the corresponding fields in the work area (see example in ).
12.Difference Between AT SELECTION-SCREEN ON and AT SELECTION-SCREEN and when exactly we go for
AT SELECTION-SCREEN ON and AT SELECTION-SCREEN ?
Name of the Event Triggering Purpose AT SELECTION-SCREEN This event is
processed before
leaving the
Selection Screen i.e. when the selection screen
has been
To Validate the input
provided through
Selection Screen.
Note: If an error message occurs in this processing block, the selection screen is redisplayed with
__
processed (at the end of PAI once
the ABAP
runtime
environment has passed all of the input data from
the selection
screen to the ABAP program).
all of its fields ready for input. This allows you to check input values for consistency.
AT SELECTION-SCREEN ON
<Field>. This event is processed before
leaving the Selection Screen Element. To Validate the Individual (Single)Input provided through Selection Screens.
Note: It Displays Only this particular Field if the Input is In Valid.
Note : We Always Validate the Only the Related Fields through AT SELECTION-SCREEN as enabling one field for INPUT is not enough , we need to enable all the Field from the Group.
Example:
If there are no Storage locations from plant P001 , Changing Only the Storage Location is not enough , we need change both Plant and Storage Location Combination and Some all Company Code, Plant and Storage Location Combination.
13.The Importance Of AT SELECTION SCREEN OUTPUT ?
This is Modify the Selection Screen. Note : For More Details, Refer Question 3.
Company Code 1000 Plant P001 Storage Location
---__
14.How Many times the Event INITIALIZATION Triggers while displaying the list of 20 Pages ,and also TOP-OF-PAGE ?
Initialization triggers only one time and TOP-OF-PAGE will trigger 20 times.
15.What is Message Class and types Of Messages and the role of PlaceHolders(&) in Messages ?
Message class is to maintain all the messages, each message is identified with 3 digit number between 000 and 999.
Types of messages : A E I S W X 1) A (abend) --- Termination. 2) E (error) --- Error.
3) I (info) --- Information. 4) S (status) --- Status message. 5) W (warning) -- warning.
6) X (Exit) --- Exit.
Note : Messages are stored in table T100, and can be maintained using Transaction SE91.
Place Holders :
Syntax to Display Message :
MESSAGE <Type><nnn> (Message ID) . Addition :
WITH f1 ... f4 . Effect :
The contents of the fields f1 are inserted into the message text to replace the placeholders &1. If you used unnumbered placeholders in your message text (&), they are replaced successively with the contents of the
__
To make messages easier to translate, ensure that you use numbered placeholders ( &1 to &4) if you need to insert more than one variable in a message text. PARAMETER P_WERKS TYPE WERKS DEFAULT ‘1000’.
PARAMETER P_LGORT TYPE LGORT DEFAULT ‘0001’.
Example : MESSAGE S009(ZEMAX) WITH P_WERKS P_LGORT. - The Storage Location &1 doesn’t exist from Plant &2.
Result of the Message :
The Storage Location 0001 doesn’t exist from Plant 1000.
Note : The &1 is replaced with P_LGORT and &2 WITH P_WERKS.
16.What is Text Symbol and the importance of Text Symbol ?
Text symbol is used to provide titles for blocks in the SELECTION SCREEN, Comments on the SELECTION SCREEN, Column Headings While Displaying the Data.
Note : Language Translations can be maintained for Text Symbols so that the same Output and Selection Screen can be used in all the required Regional Languages by Simply maintaining the same ,instead of Re-write the program in the regional language.
17.What is text element and the importance of Text Element in Reports ?
Text elements allow you to store texts without hard-coding them in
your program. You can maintain text elements outside the program in which they are used (choose Go to -> Text elements in the Editor). They are particularly important for texts in applications that will be translated into other languages ABAP has the following kinds of text element:
__ List heading
Column heading
Selection texts (for texts belonging to selection criteria and program parameters) Text symbols (constant texts)
18.What is FOR ALL ENTIRES and the mandatory things to be Checked While Using FOR ALL Entries ?
You can use the option FOR ALL ENTRIES to replace nested select loops by operations on internal tables. This can significantly improve the performance for large sets of selected data.
"For all entries in" 3 pitfalls :
select shkzg wrbtr saknr "debit/credit indicator, amount, GL acct from bseg into table t_bseg
for all entries in it_bkpf
where belnr = it_bkpf-belnr and bukrs = 'CUR '.
This is the equivalent of saying "select distinct shkzg wrbtr saknr"
Duplicates are removed from the answer set as if you had specified "SELECT DISTINCT"... So unless you intend for duplicates to be deleted include the unique key of the detail line items in your select statement. It will only pick up one line item if multiple line items appear with the same debit/credit indicator, amount and GL Account. If you want all occurrences of these you must have a select statement that includes the table's unique key, also called primary key.
Instead Do:
SELECT bukrs belnr gjahr buzei shkzg wrbtr saknr "bseg unique key + d/c ind, amt, GL acct from BSEG into table t_bseg for all entries in t_bkpf where belnr = t_bkpf-belnr and bukrs = 'CUR '.
FOR ALL ENTRIES IN...acts like a range table, so that if the "one" table is empty, all rows in the "many" table are selected. Therefore make sure you check that the "one" table has rows before issuing a select with the "FOR ALL ENTRIES IN..." clause.
__ IF NOT IT_BKPF IS INITIAL.
SELECT BUKRS BELNR GJAHR BUZEI SHKZG WRBTR SAKNR
"BSEG UNIQUE KEY + d/c ind, amt, GL acct
FROM BSEG INTO TABLE IT_BSEG
FOR ALL ENTRIES IN IT_BKPF
where belnr = it_bkpf-belnr and bukrs = 'CUR '. ENDIF. "if there are any projects
Note:So that having the IF NOT IT_BKPF IS INITIAL. Is Mandatory. If the parent table (it_bkpf) is very large there is performance degradation
19.Explain INNER and OUTER Joins ?
Specifying Two or More Database Tables as an Inner Join
In a relational database, you normally need to read data simultaneously from more than one database table into an application program. You can read from more than one table in a single SELECT statement, such that the data in the tables all has to meet the same conditions, using the following join expression:
Join Syntax : SELECT <DBT1>~f1 <DBT1>~f2 <DBT1>~f3 <DBT2>~f4 <DBT2>~f5 <DBT1>~f6 INTO TABLE <ITAB>
FROM <DBT1> INNER[LEFT OUTER JOIN] <DBT2> ON <DBT1>~f1 = <DBT2>~f2 (Join Condition)
__
INNER JOIN : Inner join expression links each line of <DBT1> (Left Hand Side Table/Master Table )with the lines in <DBT2> (Right Hand Side Table/Transactional Table )that meet the Join condition . This means that there is always one or more lines from the right-hand table that is linked to each line from the left-hand table by the join. If <DBT2> does not contain any lines that meet the Join condition, the line from <DBT1> is not included in the selection.
LEFT Outer Join :
In an inner join, a line from the left-hand database table or join is only included in the selection if there is one or more lines in the right-hand database table that meet the ON(Join) condition. The left outer join, on the other hand, reads lines from the left-hand database table or join even if there is no corresponding line in the right-hand table.
__ Example for Both Inner and Outer Join :
Entries from KNA1 Entries From KNBK(Bank Details).
JOIN On KUNNR
INNER JOIN OUTER JOIN(Always LEFT) KUNNR NAME1 BANKN BANKS
E001 eMAX ICICI 018301004245E001 eMAX ICICI 018301004245 E001 eMAX SBI 010098236655E001 eMAX SBI 010098236655
I001 iMAX
20.What is Interactive Report and Importance Of the Same ?
Interactive Reports:
Display the Summarized Information as the First List And letting the USER Interaction for the Detailed Info.
NOTE:Each interactive list event creates a new detail list.With one ABAP Program ,You can maintain one basic list and upto 20 detail lists.If the User creates a list on the
KUNNR NAME1 E001 eMAX I001 IMAX
KUNNR BANKN BANKS E001 ICICI 018301004245 E001 SBI 010098236655
__
next level(that is,SY_LSIND increases),the System stores the previous list and displays the new one.The user can interact with whichever list is currently displayed.
21.What are the Different types Of User Interaction in Interactive
Reportsand the Corresponding Events Triggered for Each type Of User Interaction ?
User can interact
Line Selection User Commands
(Double click) (Click on Function Key )
Event: AT LINE-SELECTION AT USER-COMMAND. Note:The List Index SY-LSIND will be incremented by 1 for each user Interaction. It is ZERO for Basic List , 1 for 1st 2nd ry, 2 for 2nd ry etc.upto 20
As We Can Generate Upto 20 Levels.
22.What are the Useful System Variables in Interactive Reports ?
SY-LISEL -Selected Line Contents SY-LSIND - List Index
SY-LILLI - Selected Line No
SY-UCOMM - Funcion Code of the Selected Function Key.
23.What is Role Of SET PF-STATUS in Reports ?
SET PF-STATUS... Basic form 1
SET PF-STATUS <NAME>. Additions:
__ Effect of EXCLUDING
Deactivates one or more of the status functions, so that they cannot be selected. Specify the appropriate function codes using one of the following:
A field f or a literal which contains a function code
An internal table itab which contains several function codes
24.Explain the Interactive Techniques(HIDE,SY-LISEL,GET CURSOR) in Detail ?
a)WORKING WITH HIDE TECHNIQUE:
LOOP AT IT_T001 INTO WA_T001.
WRITE : / WA_T001-BUKRS , WA_T001-BUTXT, WA_T001-ORT0. HIDE : WA_T001-BUKRS.
ENDLOOP. Actual List
From WRITE Copy in HIDE Area From HIDE
NOTE: HIDE should be always after the output (write) statement..Hide area and maintains the copy of the output(corresponding) list.
NOTE:When the user interacts with any line from any level,the system checks for the corresponding ‘HIDE’ area and Picks up the corresponding selected line contents, If HIDE Area Found, it stores the selected line Contents Back from HIDE Area to the variables(WA) through which the HIDE area is generated.
b)GET CURSOR E001 eMAX I001 iMAX
E001 eMAX I001 iMAX
__
It is used to pass the output fields or output line on which the cursor was positioned during the interactive event to the abap program
Syntax :
GET CURSOR FIELD <V_FNAM> VALUE <V_FAVL>. Which returns the Selected Field Name and Selected Field Value. c)SY-LISEL
Contents of the line from which the event was triggered
d)READ LINE
To read the line from list after an interactive list event
READ LINE <LineNo> FIELD VALUE INTO <List Of Fields>. 25.What is the Role of SY-UCOMM in Interactive Reports ?
When the user interacts with any of the application on the tool bar the event “AT USER COMMAND” will be triggered at the same time the function code of the selected button will be saved into the system variable “SY-UCOMM”
26.Explain the Purpose Of Each event in Both Classical and Interactive Reports?
EVENTS
:-Name of the Event Triggering Purpose INITIALIZATION This event occurs
before the standard selection screen is called.
To initialize the input fields of the standard selection screen AT SELECTION-SCREEN This event is
processed before
leaving the
Selection Screen i.e. when the selection screen has been processed (at the end of PAI once the ABAP runtime environment has
To Validate the input provided through Selection Screen. Note: If an error message occurs in this processing block, the selection screen is redisplayed with all of its fields ready for input. This allows you to check input values for consistency.
__
passed all of the input data from the selection screen to
the ABAP
program).
START-OF-SELECTION: This event occurs after the selection screen has been
processed and
before data is read using the logical database.
Note:-The REPORT statement always executes a
START-OF-SELECTION implcitly
consequently all processing logic
i.e, non-declarative statements that occur between the REPORT
or PROGRAM
statement and the first processing block are also processed in the
START-OF-SELECTION block. TOP-OF-PAGE: This is a list
processing event executed before the first data is output on a new page. This is processed only when generating basic list. This is only executed before outputting the first line using any output statement such as write , uline, skip on a new page. Note: It is not triggered by a NEW-PAGE
statement.
This allows you to define output which supplements the standard page header at the beginning of the page.
__
END-OF-PAGE: This will be triggered when it reaches the End-Of-Page.
This is used to print the same Footer details for all the pages.
END-OF-SELECTION: This is the last of the events called by
the runtime
environment to occur.
It is triggered after all of the data has been read from the logical database, and before the list processor is started.
Used to print the final output . Used to print Grand Totals when working with Logical Database.
AT LINE-SELECION Trigger for Line Selection from the Output List
Used to Print the Secondary List based on the Selected Line Contentes
AT USER-COMMAND Triggers for the User Interaction through Function Keys
To Validate User Command and Display the secondary list . TOP-OF-PAGE DURING
LINE-SELECTION
Triggers On top of each Secondary List
To Print the Header On the Secondary Lists
30. How to Print Different Page Headers On Each Page using the TOP-OF-PAGE ?
TOP-OF-PAGE.
__ WHEN 1. WRITE ‘PAGE1’. WHEN 2. WRITE ‘PAGE2’. WHEN OTHERS. WRITE ‘OTHERS’. ENDCASE.
31. What Happens If the Same EVENT is written twice in the Program ?
START-OF-SELECTION. Write / ‘Welcome to eMAX’. START-OF-SELECTION. Write / ‘Welcome to eMAX’.
Both the START-OF-SELECTION will be Executed in the Same Order. Out Put : WelCome to eMAX
WelCome to eMAX
32.List down any 15 tables and 5 fields from Each Table from Modules MM,SD,FI and HR?
List of MM Tables :
Table Description FiledNam Description
EBAN Purchase
Requisition
BSAKZ Control indicator for purchasing document type
LOEKZ Deletion indicator in purchasing document STATU Processing status of purchase requisition
ESTKZ Creation indicator (purchase
requisition/schedule lines)
FRGKZ Release indicator
EINA Purchasing Info
Record: General Data
INFNR Number of purchasing info record
MATNR Material number
MATKL Material group
LIFNR Vendor's account number
LOEKZ Purchasing info: General data flagged for deletion
__
Table Description FiledNam Description T001L Storage
Locations
WERKS Plant
LGORT Storage location
LGOBE Description of storage location
SPART Division
XLONG Negative stocks allowed in
storage location T001W Plants/Branches MANDT Client
WERKS Plant
NAME1 Name
BWKEY Valuation area
KUNNR Customer number of plant
RKPF Document Header:
Reservation RSNUM Numberreservation/dependent of
requirements
KZVER Origin
XCALE Check date against factory
calendar
RSDAT Base date for reservation
USNAM User name
RSEB RESERVATION/ DEPENDANT REQUIREMENTS MANDT Client RSNUM Number of reservation/dependent requirements
RSPOS Item number of
reservation/dependent requirements
RSART Record type
__
Table Description FiledNam Description MLGN Material Data for
Each Warehouse Number
MANDT Client
MATNR Material number
LGNUM Warehouse Number /
Warehouse Complex
LVORM Deletion flag for all material data of a warehouse number
LGBKZ Storage section indicator
MARA General Material Data
MANDT Client
MATNR Material number
ERSDA Creation date
ERNAM Name of Person who Created the Object
LAEDA Date of last change
MARC Plant Data for Material
MANDT Client
MATNR Material number
WERKS Plant
PSTAT Maintenance status
LVORM Flag Material for Deletion at Plant Level
__
Table Description FiledNam Description
MARM Units of
Measure for Material
MANDT Client
MATNR Material number
MEINH Alternative unit of
measure for
stockkeeping unit
UMREZ Numerator for
Conversion to Base Units of Measure
UMREN Denominator for
conversion to base units of measue
MAKT Material
Description
MANDT Client
MATNR Material number
SPRAS Language key
MAKTX Material description
MAKTG Material description in upper case for matchcodes
LAGP Storage bins MANDT Client
LGNUM Warehouse Number /
Warehouse Complex
LGTYP Storage Type
LGPLA Storage bin
LGBER Storage section
MGEF Hazardous
materials
MANDT Client
STOFF Hazardous material
number
REGKZ Region code
LAGKL Storage class
WGFKL Water pollution
__
Table Description FiledNam Description
VBAK Sales Document:
Header Data
VBELN Sales document
ERDAT Date on which the record was
created
ERZET Entry time
ERNAM Name of Person who Created the Object
ANGDT Quotation/Inquiry is valid from
VBAP Sales Document:
Item Data MANDTVBELN Sales documentMaterial number
POSNR Sales document item
MATNR Material number
MATWA Material entered
VBRK Billing: Header
Data
VBELN Billing document
FKART Billing type
VBTYP SD document category
FKTYP Billing category
WAERK SD document currency
VBRP Billing: Item Data VBELN Billing document
POSNR Billing item
UEPOS Higher-level item in bill of material
structures
FKIMG Actual billed quantity
VRKME Sales unit
VBFA Sales Document
Flow
VBELV Preceding sales and distribution
document
POSNV Preceding item of an SD document
VBELN Subsequent sales and distribution document
POSNN Subsequent item of an SD document
VBTYP_N Document category of subsequent document
VBRL SD Document:
Invoice List
VBELN Invoice list
POSNR Invoice list item
VBELN_VB Billing document
NETWR Net value in document currency
__
Table Description FiledNam Description
VBEH SCHEDULE LINE
HISTORY
VBELN Sales document
POSNR Sales document item
ETENR Schedule line
ABRLI Internal delivery schedule number
ABART Release type
VBEP Sales
DocumentSchedule Line Data
ETENR Schedule line
ETTYP Schedule line category
LFREL Item is relevant for delivery
EDATU Schedule line date
EZEIT Arrival time
VBUK Sales Document:
Header Status and Administrative Data
MANDT Client
VBELN Sales and distribution document
number
RFSTK Reference document header status
RFGSK Total reference status of all items
BESTK Confirmation status
VBUP Sales Document:
Item Status MANDTVBELN ClientSales and distribution document number
POSNR Item number of the SD document
RFSTA Reference status
RFGSA Overall status of reference
KNKA Customer master
credit
management: Central data
MANDT Client
KUNNR Customer number
KLIMG Credit limit: Total limit across all control areas
KLIME Credit limit: Limit for individual control area
__
List of HR TABLEs:
Table Description FiledNam Description
KNKK Customer Credit
Control Data
KKBER Client
KKBER Customer number
KKBER Credit control area
KLIMK Customer's credit limit
KNKLI Customer's account number with
credit limit reference
KNA1 General Data in
Customer Master
MANDT Client
KUNNR Customer number
LAND1 COUNTRY1 NAME1 NAME1 ORT01 CITY KNB1 Customer Master (Company Code) MANDT Client
KUNNR Customer number
BUKRS Company Code
PERNR Personnel Number
SPERR Posting block for company code
KNBK Customer Master
(BANK DETAILS)
MANDT Client
KUNNR Customer number
BANKS Bank country key
BANKL Bank key
BANKN Bank account number
KNB4 Customer Payment
History MANDTKUNNR ClientCustomer number
BUKRS Company Code
AUFZD Date as from when the payment history was recorded
JAH01 Calendar Year
KNB5 Customer master
(dunning data) MANDTKUNNR ClientCustomer number
BUKRS Company Code
MABER Dunning Area
__
Table Description FiledNam Description PA0160 HR master record,
infotype 0160
(Family allowance)
CDANF Family allowance indicator
TPAN1 Family allowance type
NRCT1 Number of member for count type
TPAN2 Family allowance type
RECOM Total income
PA0167 HR Master Record: Infotype 0167 (Health Plans)
BAREA Benefit area
PLTYP Benefit plan type
BPLAN Benefit plan
BENGR Benefit first program grouping
BSTAT Benefit second program grouping
PA0168 Customer Master (Company Code)
PERNR Personnel number
SUBTY Subtype
OBJPS Object Identification
SPRPS Lock Indicator for HR Master Data
Record
SEQNR Number of Infotype Record With
Same Key PA0169 HR Master Record:
Infotype 0169 (Savings Plan))
ENRTY Benefit type of plan enrollment
EVENT Benefit adjustment reason
PERIO Benefit period for calculations
EEAMT Benefit employee pre-tax
contribution amount
EEPCT Benefit EE pre-tax contribution
percentage PA0021 HR Master Record:
Infotype 0021 (Family)
FAMSA Type of family record
FGBDT Date of Birth
FGBLD Country of Birth
FANAT Nationality
FASEX Gender Key
PA0022 HR Master Record: Infotype 0022 (Education)
SLART Educational establishment
INSTI Institute/location of training
SLAND Country key
AUSBI Education/training
__
Table Description FiledNam Description PA0023 HR Master Record:
Infotype 0023 (Other/Previous Employers)
ARBGB Name of employer
ORT01 City
LAND1 Country key
BRANC Industry key
TAETE Job at former employer(s)
PA0024 HR Master Record: Infotype 0024 (Qualifications)
QUALI Qualification key
AUSPR Proficiency of a
Qualification/Requirement
RESE1 Reserved Field/Unused Field of
Length 2
ITBLD Name of appraiser
PA0025 HR Master Record: Infotype 0025 (Appraisals)
BWNAM Personnel number
DAT25 Appraisal date
LWKJN Flag: Affects remuneration
KENJN Indicator: Notified
GRPNR Group number (appraisals)
PA0008 HR Master Record: Infotype 0008 (Basic Pay)
TRFAR Pay scale type
TRFGB Pay scale area
TRFGR Pay Scale Group
TRFST Pay Scale Level
STVOR Date of next increase
PA0005 HR Master Record: Infotype 0009 (Bank Details)
OPKEN Operation Indicator for Wage Types
BETRG Standard value
ANZHL Standard Percentage
ZLSCH Payment Method
EMFTX Payee Text
PA0009 HR Master Record: Infotype 0005 (LeaveEntitlement)
URLJJ Leave year
URBEG Start of leave
UREND Start of leave
UAR01 Leave type
__
FICO TABLES:
Table Description FiledNam Description PA0045 HR Master Record:
Infotype 0045 (Company Loans)
EXTDL External Reference Number
DATBW Approval date
DARBT Loan amount granted
DKOND Loan conditions
TILBG Repayment start
PA0074 HR Master Record: Infotype 0074 (Leave Processing - DK)
FEORD Leave provision - Denmark
FGPCT Vacation Bonus Savings Percentage
Rate - Denmark
FTPCT Percentage of Vacation Bonus
(Denmark)
FPFRE Vacation Bonus / Transfer /
Payment Frequency PA0143 HR Master Record:
Infotype 0143 (Life Insurance JP)
INSID Insurance Type Indicator
INSCC Insurance company master JPN
INSNR Insurance No.
INSMP Insurance deduction of monthly
payroll
__
Table Description FiledNam Description
B006 SOrg/DstCh/Division/Customer KAPPL Application
KSCHL Output type
VKORG Sales organization
VTWEG Distribution channel
SPART Division
TVRO Routes MANDT Client
ROUTE Route
TRAZT Outdated: Transit Time from GI
to Ship-to Party (in Days)
TRAZTD Transit duration in calendar days
TVST Organizational Unit: Shipping Points
MANDT Client
VSTEL Shipping point/receiving point
FABKL Factory calendar key
VTRZT Rounding-up period for
delivery scheduling (in days)
ADRNR Address
BSAD Accounting: Secondary Index
for Customers (Cleared Items)
MANDT Client
BUKRS Company Code
UMSKS Special G/L Transaction Type
UMSKZ Special G/L Indicator
BSAK Accounting: Secondary Index
for Vendors (Cleared Items)
BUKRS Company Code
LIFNR Account number of vendor or creditor
UMSKS Special G/L Transaction Type
UMSKZ Special G/L Indicator
AUGDT Clearing Date
BSAS Accounting: Secondary Index
for G/L Accounts (Cleared Item)
MANDT Client
BUKRS Company Code
HKONT General ledger account
AUGDT Clearing Date
AUGBL Document Number of the
__
Table Description FiledNam Description
BSID Accounting: Secondary Index
for Customers
UMSKS Special G/L Transaction Type
UMSKZ Special G/L Indicator
AUGDT Clearing Date
AUGBL Document Number of the
Clearing Document
ZUONR Assignment number
BSIK Accounting: Secondary Index
for Vendors
LIFNR Account number of vendor or creditor
UMSKS Special G/L Transaction Type
UMSKZ Special G/L Indicator
AUGDT Clearing Date
BSIS Accounting: Secondary Index
for G/L Accounts
HKONT General ledger account
AUGDT Clearing Date
AUGBL Document Number of the
Clearing Document
ZUONR Assignment number
GJAHR Fiscal year
BNKA Bank master record BANKS Bank country key
BANKL Bank key
ERDAT Date on which the record was
created
ERNAM Name of person who created the
object
BKPF Accounting Document Header MANDT Client
BUKRS Company Code
BELNR Accounting document number
GJAHR Fiscal year
BLART Document type
BSEG Accounting Document Segment MANDT Client
BUKRS Company Code
BELNR Accounting document number
GJAHR Fiscal year
BUZEI Number of Line Item Within Accounting Document
__
Table Description FiledNam Description
CSKS Cost Center Master Data MANDT Client
KOKRS Controlling Area
KOSTL Cost Center
DATBI Valid to date
DATAB Valid-from date
CSKT Cost Center Texts MANDT Client
SPRAS Language key
KOKRS Controlling Area
KOSTL Cost Center
CSLA Activity master MANDT Client
KOKRS Controlling Area
LSTAR Activity Type
DATBI Valid to date
DATAB Valid-from date
CSLT Activity type texts MANDT Client
SPRAS Language key
KOKRS Controlling Area
LSTAR Activity Type
CSSL Cost Center / Activity Type KOKRS Controlling Area
KOSTL Cost Center
LSTAR Activity Type
GJAHR Fiscal year
CCKEY Cost collector key
CSSK Cost center /cost element MANDT Client
VERSN VERSIONS
KOKRS Controlling Area
GJAHR Fiscal year
__
.
26.Explain the Flow Of MM,SD,FI/CO ?
Table Description FiledNam Description CEPC Profit Center Master Data
Table
PRCTR Profit center
DATBI Valid to date
KOKRS Controlling Area
DATAB Valid-from date
__
The Key Terms Used in MM.
MM Organization
Structure
Client Storage location 1 Storage location 2 WH WH Plant 4 Plant 3 Plant 1 Plant 2 Purchasing Organization 2Company code 1 Company code 2
Storage location 1 Storage location 1 Purchasing Organization 1
__
A Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.
A Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the company’s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year.
Company Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.
__
Plant : is an Organizational Logistics Unit that Structures the Organization From the Perspective of Production, Procurement and Materials Planning.
• A purchasing organization is an organizational level that negotiates conditions of purchase with vendors for one or more plants. It is legally responsible for completing purchasing contracts.
• A purchasing group is the key for a buyer or group of buyers responsible for certain purchasing activities.
Storage location : is an organizational unit that allows the differentiation of material stocks within a plant.
Inventory Management on a quantity basis is carried out at storage location level in the plant. Physical inventory is carried out at storage location level.
The Key Areas in Materials Management : 1. Purchasing(Procurement)
2. Materials Requirement Planning(MRP) 3. Inventory Management & Physical Inventory
1) Purchasing(Procurement)
(MM Flow)
Purchasing is a component of Materials Management (MM). The Materials Management (MM) module is fully integrated with the other modules of the SAP System.
__
Process Flow in Detail :
The typical procurement cycle for a service or material consists of the following phases:
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. 1.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.
2.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.
3.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.
__
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.
5Goods 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 under deliveries of ordered goods. 6.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.
7.Payment Processing
Integration
Purchasing communicates with other modules in the SAP System to ensure a constant flow of information. For example, it works side by side with the following modules: Controlling (CO)
The interface to the cost accounting system (Controlling) can be seen above all in the case of purchase orders for materials intended for direct consumption and for services, since these can be directly assigned to a cost center or a production order.
Financial Accounting (FI)
Purchasing maintains data on the vendors that are defined in the system jointly with Financial Accounting. Information on each vendor is stored in a vendor master record, which contains both accounting and procurement information. The vendor master record represents the creditor account in financial accounting.
__
Through PO account assignment, Purchasing can also specify which G/L accounts are to be charged in the financial accounting system.
Sales and Distribution (SD)
Within the framework of materials planning and control, a requirement that has arisen in the Sales area can be passed on to Purchasing. In addition, when a requisition is created, it can be directly assigned to a sales order.
Purchasing Document Definition
A purchasing document is an instrument used by Purchasing to procure materials or services.
The following list shows the various external purchasing documents available in the standard SAP System. (Note: purchase requisitions are not included on this list because they are usually regarded as internal documents used within Purchasing and are therefore treated separately.)
__
Request for quotation(RFQ)
Transmits a requirement defined in a requisition for a material or service to potential vendors.
Quotation
Contains a vendor's prices and conditions and is the basis for vendor selection. Purchase order (PO)
The buying entity’s request or instruction to a vendor (external supplier) to supply certain materials or render/perform certain services/works, formalizing a purchase transaction.
Contract
In the SAP Purchasing component, a type of "outline agreement", or longer-term buying arrangement. The contract is a binding commitment to procure a certain material or service from a vendor over a certain period of time.
Scheduling agreement
Another type of "outline agreement", or longer-term buying arrangement. Scheduling agreements provide for the creation of delivery schedules specifying purchase
__
quantities, delivery dates, and possibly also precise times of delivery over a predefined period.
Requirements of materials or services can be reported to Purchasing by means of purchase requisitions.
Structure
Each purchasing document is subdivided into two main areas: the header and individual items. Each document will contain a header and can contain several items. The header contains information relevant to the whole document . The items specify the materials or services to be procured. For example, information about the vendor and the document number is contained in the document header, and the material description and the order quantity are specified in each item.
Master Records from the Purchasing View
This section describes the functions of the material master and vendor master records that specifically relate to purchasing. It discusses purchasing-specific master data and describes how to enter and maintain material and vendor data relating to purchasing.
__
MM Purchasing processes the following types of Master data:
Material Master Data : Details on materials an enterprise procures externally or produces in-house. The unit of measure and the description of a material are examples of the data stored in a material master record. Other SAP Logistics components also access the material data.
Vendor Master Data : Information about external suppliers (creditors). The vendor’s name and address, the currency the vendor uses, and the vendor number (stored in the SAP system as an account number) are typical vendor data.
Purchasing Master Data : such as the following: Purchasing Info Record
The info record establishes the link between material and vendor, thus facilitating the process of selecting quotations. For example, the info record shows the unit of measure
__
used for ordering from the vendor, and indicates vendor price changes affecting the material over a period of time.
Source List
The source list specifies the possible sources of supply for a material. It shows the time period during which a material may be ordered from a given vendor.
Quota Arrangement
The quota arrangement specifies which portion of the total requirement of a material over a certain period is to be assigned to particular vendors on the basis of quotas. Purchase Requisitions :
You use this component if you wish to give notification of requirements of materials and/or external services and keep track of such requirements.
Requisitions can be created either directly or indirectly.
"Directly" means that someone from the requesting department enters a purchase requisition manually. The person creating the requisition determines what and how much to order, and the delivery date.
"Indirectly" means that the purchase requisition is initiated via another SAP component.
RFQ and Quotation:
You use this component if you wish to manage and compare requests for quotation (RFQs) issued to vendors and the quotations submitted by the latter in response to them.
__
In Purchasing, the RFQ and the quotation form a single document. Prices and conditions quoted by vendors are entered in the original RFQ. If you have issued an RFQ to several vendors, you can have the system determine the most favorable quotation submitted and automatically generate letters of rejection to the unsuccessful bidders. You can also store the prices and terms of delivery from certain quotations in an info record for future accessing.
Purchase Orders : Definition
A purchase order is a formal request or instruction from a purchasing organization to a vendor or a plant to supply or provide a certain quantity of goods or services at or by a certain point in time.
The purchase order can be used for a variety of procurement purposes. You can procure materials for direct consumption or for stock. You can also procure services. Furthermore, the special procurement types "subcontracting", "third-party" (involving triangular business deals and direct-to-customer shipments) and "consignment" are possible.
You can use purchase orders to cover your requirements using external sources (i.e. a vendor supplies a material or performs a service). You can also use a purchase order to procure a material that is needed in one of your plants from an internal source, i.e. from another plant. Such transactions involve longer-distance stock transfers. The activities following on from purchase orders (such as the receipt of goods and invoices) are logged, enabling you to monitor the procurement process.
You can use purchase orders for once-only procurement transactions. If, for example, you wish to procure a material from a vendor only once, you create a purchase order. If you are thinking of entering into a longer-term supply relationship with this vendor, it is advisable to set up a so-called outline agreement, since this usually results in more favorable conditions of purchase.
The procedures and menu paths described in the SAP Library refer to the traditional purchase order (ME21, ME22, ME23) and not to the Enjoy purchase order (ME21N, ME22N, ME23N).
__
Structure
A purchase order (PO) consists of a document header and a number of items.
The information shown in the header relates to the entire PO. For example, the terms of payment and the delivery terms are defined in the header. A procurement type is defined for each of the document items. The following procurement types exist:
__ • Standard • Subcontracting • Consignment • Stock transfer • External service
Incoterms: Incoterms are internationally-recognized terms of delivery reflecting the standards set by the International Chamber of Commerce (ICC). For example, the term Free on Board (FOB) means that seller fulfills his obligation to deliver when the goods have passed over the ship’s rail at the named port of shipment. This means that the buyer has to bear all costs and risks of loss of or damage to the goods from that point. You can specify Incoterms for an order item that differ from those in the PO header. The relevant defaults come from the purchasing info record. When the document is outputted, the item-specific Incoterms are set out in addition to the generally applicable ones at header level.
Shipping Instructions
These are the packing instructions the vendor has to comply with when shipping the ordered materials. You specify them for an item by entering the predefined code for shipping instructions. The corresponding text is then included in the purchasing document printout.
__
Purpose
The central role of MRP(Materials Requirements Planning) is to monitor stocks and in particular, to automatically create procurement proposals for purchasing and production (planned orders, purchase requisitions or delivery schedules). This target is achieved by using various materials planning methods which each cover different procedures.
Method 1: CBP(Consumption Based Planning) :
27) Explain the Flow Of SD ? 28) Explain the Flow of FI ?
Reorder Point Planning : In reorder point planning, procurement is triggered when the sum of plant stock and firmed receipts falls below the reorder point.
The reorder point should cover the average material requirements expected during the replenishment lead time.
Consumption based planning
To determine : Which material to order When to order
Quantity required / Quantity to order.
C B P determines the requirement based on past consumption .
it is triggered when stock levels fall below a predefined reorder point or by
__
The safety stock exists to cover both excess material consumption within the replenishment lead time and any additional requirements that may occur due to delivery delays. Therefore, the safety stock is included in the reorder level.
Manual Reorder Point Planning
In manual reorder point planning, you define both the reorder level and the safety stock level manually in the appropriate material master.
Automatic Reorder Point Planning
In automatic reorder point planning, both the reorder level and the safety stock level are determined by the integrated forecasting program.
The system uses past consumption data (historical data) to forecast future requirements. The system then uses these forecast values to calculate the reorder level and the safety stock level, taking the service level, which is specified by the MRP controller, and the material's replenishment lead time into account, and transfers them to the material master.
Forecast-Based Planning
Forecast-based planning is also based on material consumption. Like reorder point planning, forecast-based planning operates using historical values and forecast values and 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. The forecast values therefore have a direct effect in MRP as forecast requirements.
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.
Materials that are planned using the time-phased planning technique are provided with an MRP date in the planning file. This date is set when creating a material master 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.
3.
Managing Stocks by Quantity
All transactions that bring about a change in stock are entered in real time, as are the stock updates resulting from these changes. You can obtain an overview of the current stock situation of any given material at any time. This, for example, applies to stocks that:
• Are located in the warehouse
• Have already been ordered, but have not yet been received
• Are located in the warehouse, but have already been reserved for production or a customer
• Are in quality inspection. Managing Stocks By Value
The stocks are managed not only on a quantity basis but also by value. The system automatically updates the following data each time there is a goods movement:
Inventory
Management
Functions of Inventory Management : To manage the stocks on a quantity
value basis Plan, enter & check the goods movements like :
Goods receipts
Goods issue
Transfer postings
To carryout the physical inventory .
__
• Quantity and value for Inventory Management
• Account assignment for cost accounting
G/L accounts for financial accounting via automatic account assignment Planning, Entry, and Documentation of all Goods Movements
Goods movements include both "external" movements (goods receipts from external procurement, goods issues for sales orders) and "internal" movements (goods receipts from production, withdrawals of material for internal purposes, stock transfers, and transfer postings).
For each goods movement a document is created which is used by the system to update quantities and values and serves as proof of goods movements.
You can print goods receipt/issue slips to facilitate physical movements and monitor the individual stocks in the warehouse.
Goods Movement : Transaction resulting in a change in stock.
Goods Movement Goods Receipt Goods Issue Transfer postings Physical Inventory Reservation
__ Structure
• Goods receipt
A goods receipt (GR) is a goods movement with which the receipt of goods from a vendor or from production is posted. A goods receipt leads to an increase in warehouse stock.
• Goods issue
A goods issue (GI) is a goods movement with which a material withdrawal or material issue, a material consumption, or a shipment of goods to a customer is posted. A goods issue leads to a reduction in warehouse stock.
The Inventory Management system supports the following types of goods issues:
• Withdrawal of material for production orders
• Scrapping and withdrawal of material for sampling
• Return deliveries to vendors
• Other types of internal staging of material
Deliveries to vendors without the involvement of the SD Shipping component
• Stock transfer
A stock transfer is the removal of material from one storage location and its transfer to another storage location. Stock transfers can occur either within the same plant or between two plants.
• Transfer posting
A transfer posting is a general term for stock transfers and changes in stock type or stock category of a material. It is irrelevant whether the posting occurs in conjunction with a physical movement or not. Examples of transfer postings are:
• Transfer postings from material to material
• Release from quality inspection stock
