SAP LOGISTICS I SAP MM | Procure To Pay Cycle

SAP (System Application and Products in Data Processing) ERP has many modules.

SAP Logistics is one of them. Logistics are incorporates following modules: 

• Sales and Distribution, 
• Production Planning, 
• Plant Maintenance, 
• Project Systems, 
• Warehouse Management 
• Materials Management module.
• SAP MM deals with the material management and inventory management
• MM process ensures that there is never a shortage of materials,
• SAP MM speeds up the procurement and material management activities making the run business smoother with complete time and cost efficiency.
• the aim is to accelerating the productivity.
•  Reducing cost
• Deals with procurement process, master data (Material and vendor) , account determination and valuation of material, Inventory

Procurement Cycle :

A brief introduction of Procurement activities is given below:

Procurement Activities	Description
Determination of requirement	It is the logical subdivision where it is determined that what material or services are required to company, and which supplier can fulfill the requirement.
Creating Purchase Requisition	It is the phase in which purchasing department is informed about the requirement of items or services required for business purpose. A requisition is a internal document.
Creating Purchase Order	It is the phase when order is created from requisition and it is approved and assigned to a supplier.
Goods receipt/ Invoice Received	It is the phase in which the material is received by the company and the condition and quality are verified. In this phase Invoice is received from the vendor (seller).
Invoice verification/ Vendor Payment	It is the phase in which the vendor (seller) is paid from the company and reconciliation of the invoice and PO is accomplished.

Procurement for Stock vs Consumption

The following points show the difference of Procurement for Stock vs. Consumption:

• Procurement for Stock - A stock material is a material that is kept in stock. These materials are kept in stock once received from the vendor. The stock of this material keeps on increasing or decreasing based on amount of the quantity received or issued. To order a material for stock, the material must have a master record within the system.
• Procurement for Direct Consumption - When procurement is for direct consumption i.e. it will be consumed as soon as it is received, the user should specify the consumption purpose. To order a material for consumption, the material may have a master record within the system.

Special Procurement : 

Consignment Stocks

Material that is available at our store premises, however it still belongs to the vendor (seller)/Owner of the material. If you utilize the material from consignment stocks, then you have to pay to the vendor.

Third-party processing

In third-party processing, a company passes on a sales order to associate external vendor (seller) who sends the goods directly to the customer. The sales order is not processed by your company, however by the vendor (seller). Third-party items can be entered in purchase requisitions, purchase orders and sales orders.

Pipeline handling

In pipeline handling, the company needs not to order or store the material involved. It is obtainable as and when required via a pipeline (for example, oil or water), or another style of cable (such as electricity). The material that is consumed is settled with the vendor (seller) on a regular basis.

Returnable Transport Stock

The company orders goods from a vendor (seller). The goods are delivered with returnable transport packaging (pallets, containers) that belongs to the vendor (seller) and is stored on the customer premises until they return it to the company.

Subcontracting

The vendor (the subcontractor) receives components from the ordering party with the help of which it produces a product. The product is ordered by your company through a purchase order. The components required by the vendor (seller) to manufacture the ordered product are listed in the purchase order and provided to the subcontractor.

Stock transfer using stock transport order

Goods are procured and supplied within a company. One plant order the goods internally from another plant (receiving plant/issuing plant). The goods are procured with a special type of purchase order - the stock transport order. You'll be able to request and monitor the transfer of goods with a stock transport order.

The Organizational Structure in MM consists of following Organizational Levels:

• Client - Client is a commercial organizational unit in R/3 system.
• Company Code (OX15 OX02)- Independent accounting unit. 
• Plant (OX10) - Independent unit where activities take place. A plant produce goods and makes goods available for the company. that has own profit, loss and balance statement.
• Storage Location(OX09) - differentiates between different material stocks in a plant. where stock is kept physically.
• Purchasing Organization (OX08) - Purch Org is an org unit under company or plant which is responsible for procurement activities according to requirements. can be company specific or plant specific. 
• Purchasing Group(OME4) - responsible for everyday procurement activities within an organisation.

Four basic and must assignments in standard SAP are:

• Plant to Company code - OX18
• Purchasing organization to company code - OX01
• Purchasing organization to Plant - OX17
• Standard purchasing organization to plant - SPRO

                   
SAP MM Master Data :

• Material Master Data -
•  Has for characteristics :
1. Materials Types (OSM2) : Materials with some common properties are grouped  together and they are assigned to a material group. (Raw Material, Finished products)
2. Material Groups (OMSF) : Material group is a wider range of material type. Materials with some common attributes are taken together and they are assigned to material group. For Example: Suppose we have some materials which need packaging, so there material type can be electrical or food products but we can group these material types and put them in packaged material group. 
3. Number Range (MMNR): external (you assign manually) Internal (system assign automatically). Number Ranges are defined for each material type.
4. Material Master Creation (MM01): 
• Vendor Master Data - this data will include information on vendors from which a company can procure or it can sell. Information like vendor name and address. data is divided in three categories :
1. General Data : maintained at client level valid for all org levels
2. Accounting Data : maintained at company level 
3. Purchasing Data : maintained at purchasing org level. 
• Vendor master has 3 characteristics :
1.  Vendor Account Group (OBD3)
2.  Number Range (XDN1)
3. Creation of Vendor Master (XK01)

Procure to Pay Cycle 
The steps which are required to procure a material in right quantity and at the right price, forms the Procure to Pay Cycle.

1. Determination of the requirement : What material or service is required by the company and which supplier can provide this.
2. Purchase Requisition ( ME51N) : Internal request to purchasing. PR converted to RFQ/PO/routine agreement. 
3. RFQ (ME41): Either can be created manually or automatically from PR. 
4. Purchase Order (ME21N) : Is a formal and final confirmation of the requirement which is sent to the Vendor to supply material or services. Delivery date, quantity,price, reference etc. TYpes of POs in MM are :
• Standard PO
• Subcontracting PO - Item Category L
• Consignment PO - Item Category K
• Stock Transfer PO - Item Category U
• Service PO - Item Category D 
• Planned PO
• Contract PO
5. Posting Goods Receipt (MIGO) : After Processing of PO by Vendor , goods are delivered to the ordering party and his process in called goods receipt. So, goods receipt is a process in which goods are received by the ordering party and the condition and quality are verified. Following are the steps for posting goods receipt :
1. GO to MIGO.
2. Fill all the necessary details like movement type (101 for goods receipt), name of the material, quantity received , details of storage location and plant where material going to be stored.
3. Save .
6. Posting Invoice (MIRO): This is the phase where the Vendor is paid from the company and reconciliation of the invoice and PO is accomplished. Below are the steps for posting invoice :
1. goto MIRO.
2. Fill necessary details like invoice posting date, amount that is paid to vendor along with quantity.
3. Click on save.

Inventory Management : It deals with following terms :

1. Movement Type - Describes he type of stock posting in inventory.  It represents the posting in stock is due to which type of order, like if stock is posted against goods receipt or goods issue.The Important movement types are :
1. 101 - Goods Receipt for PO 
2. 103 - GR for PO in GR blocked stock 
3. 201 - Goods Issue for a cost center 
4. 261 - Goods issue for an order
5. 301 - transfer posting plant to plant in one step 
6. 305 - transfer posting plant to plant in two steps - placement in storage 
7. 311 - transfer posting to storage location to storage location in one step
8. 313 - Stock transfer storage locations to storage location in two steps - removal from storage
9. One step transfers of materials can be posted using movement type 301. Other movement types are 303, 351, 641, or 643 in the stock transport order.
2. Goods Receipt MIGO - When order is received by ordering party. and condition and quality are verified. 
3. Reservation (MB21/MMBE) - Sometimes stock need to be blocked in advance so it can be available for a particular point of time. this is known as reservation.
4. Goods Issue MIGO -  moving stock out of inventory , this will result in decrease in quantity in warehouse.

Invoice Verification MIRO:

Blocked Invoice - To release blocked invoice use MRBR.

T-Code	Description
OX15	Create Company
OX02	Create Company Code
OX10	Create Plant
OX09	Create Storage Location
OX08	Create Purchasing Organization
OME4	Create Purchasing Group
OX18	Assign Plant to Company Code
OX01	Assign Purchasing Organization to Company Code
OX17	Assign Purchasing Organization to Plant
MM01	Create Material
MM02	Change Material
MM03	Display Material
MB51	Material Document List
MMDE	Delete All Materials
MMNR	Define Material Master Number Ranges
XK01	Create Vendor
XK02	Change Vendor
XK03	Display Vendor
ML33	Create Vendor Conditions
ME11	Maintain Purchasing Info Record
ME01	Maintain Source List
ME51N	Create Purchase Requisition
ME52N	Change Purchase Requisition
ME53N	Display Purchase Requisition
ME41	Create RFQ/Quotation
ME42	Change RFQ/Quotation
ME43	Display RFQ/Quotation
ME31L	Create Scheduling Agreement
ME32L	Change Scheduling Agreement
ME33L	Display Scheduling Agreement
MEQ1	Create Quota Arrangement
MEQ2	Change Quota Arrangement
MEQ3	Display Quota Arrangement
ME21N	Create Purchase Order
ME22N	Change Purchase Order
ME23N	Display Purchase Order
ME29N	Release Purchase Order
ME59N	Automatic generation of Purchase Order
MIGO	Post Goods Movement
MB1A	Goods Withdrawal
MB1B	Transfer Posting
MB1C	Post Other Goods Receipts
MB01	Post Goods Receipt for Purchase Order
OMJJ	Customizing: Define New Movement Types
MIRO	Enter Incoming Invoice
MIRA	Fast Invoice Entry
MR8M	Cancel Invoice Document
MRBR	Release Blocked Invoices
OMR6	Tolerance limits: Invoice Verification
MIR5	Display List of Invoice Documents
MIR6	Invoice Overview
MIR7	Park Invoice
MRIS	Settle Invoicing Plan
AC02	Service Master
ML81N	Create Service Entry Sheet
MRRL	Evaluated Receipt Settlement
MMB1	Create Semi Finished Product
MMF1	Create Finished Product
MMG1	Create Returnable Packaging
MMH1	Create Trading Goods
MMI1	Create Operating Supplies
MMK1	Create Configurable Material
MMN1	Create Non-Stock Material
MMBE	Stock Overview
MB52	List of Warehouse Stocks on Hand
MB21	Create Reservation
MBST	Cancel Material Document
MB5T	Stock in Transit

.

OData in SAP Part 1

Source : SCN Post

How internet works:
- Your request a URL using web browser.
- Web browser sends your request to the web server using HTTP. ( HTTP defines the semantics of what the browser and web server can communicate to each other ).
- Web server then sends back HTTP response to your browser. (HTTP is stateless because, every single request received by the server is forgotten after a response has been sent across. web servers do not process HTTP requests by remembering the previous request).
- Browser parsed that HTTP response and prepare a DOM tree. DOM stands for document object   model and it is a language independent convention for representing objects in HTML.

URI vs URL:


GET and POST Methods :
- When you type a string in google search page and press enter, it actually generates a HTTP request with GET method in background. (Retrieve information from server)
- When you login to some web page using username and password and press enter, it actually generates a HTTP request with POST method in background. (send data to server)

HTTP Response:
- HTTP response comes with data and a status code.

- HTTP codes are 3 digit integers.

Code and Description

1xx: Informational It means the request has been received and the process is continuing.

2xx: Success It means the action was successfully received, understood, and accepted.

3xx: Redirection It means further action must be taken in order to complete the request.

4xx: Client Error It means the request contains incorrect syntax or cannot be fulfilled.

5xx: Server Error It means the server failed to fulfill an apparently valid request.

For example, status code 400 means Bad Request. It means that the server did not understand the request.

SAP ABAP ALV

There are total four types of views, based on the way in which the view is implemented and the methods that are permitted for accessing the view data. They are - Database Views, Projection Views, Maintenance Views, and Helps Views,.


Among these four types of database views, only 'Database Views' implements INNER JOIN, rest all implements an OUTER JOIN. The detail description of each views has been discussed further below.

- Database View (SE11)

Database views are implement an inner join, that is, only records of the primary table (selected via the join operation) for which the corresponding records of the secondary tables also exist are fetched. Inconsistencies between primary and secondary table could, therefore, lead to a reduced selection set.

- Help View ( SE54)

Help views are used to output additional information when the online help system is called.

When the F4 button is pressed for a screen field, a check is first made on whether a matchcode is defined for this field. If this is not the case, the help view is displayed in which the check table of the field is the primary table. Thus, for each table no more than one help view can be created, that is, a table can only be primary table in at most one help view.

 - Projection View

Projection views are used to suppress or mask certain fields in a table (projection), thus minimizing the number of interfaces. This means that only the data that is actually required is exchanged when the database is accessed.

A projection view can draw upon only one table. Selection conditions cannot be specified for projection views.

- Maintenance View ( SE54 )

Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.

========================================================================

ABAP Reports:
classical and interactive:

- SY-LSIND - list number from 0 to 21.
- SY-lisel - contains data of selcted line.
- Interactive report events:

1. At line selection
2. AT user command 
3. AT PFn
4. TOP-OF-PAGE during line selection

ABAP Report Types

ABAP report types are those ones available in some report's attributes screen, i.e. :

Executable program

Function group (containing function modules)

Include

Interface pool

Class pool

Module pool

Subroutine pool

=======================================================================

========================================================================

ABAP List Viewer :

Also ALV means ABAP List Viewer. Most convenient way to use it is through reuse library (cf. transaction se83) available from release 4.6 of SAP R/3.

ALV is available in two modes: list and grid. List mode is good old list processing with standard functionnalities, and grid mode is using a new OCX object displaying grids 

- CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM       = 'Prog.name'
            I_STRUCTURE_NAME         = 'I_ITAB'
            I_DEFAULT                = 'X'
            I_SAVE                   = 'A'
       TABLES
            T_OUTTAB                 = I_ITAB.
  IF SY-SUBRC <> 0.
    WRITE: 'SY-SUBRC: ', SY-SUBRC .
  ENDIF.

- FM REUSE_ALV_COMMENTRY_WRITE to add logo in your report output.
- you can first upload image in tcode OAER.

- REFRESH_TABLE_DISPLAY to refresh the alv grid.
- I_SOFT_REFRESH , used to display only Icons.
========================================================================

SALV:

        CALL METHOD CL_SALV_TABLE=>FACTORY
          IMPORTING
            R_SALV_TABLE = O_ALV
          CHANGING
            T_TABLE      = T_MARA.
      CATCH CX_SALV_MSG INTO LC_MSG .
    

* Calling Set PF status method
    CALL METHOD SET_PF_STATUS
      CHANGING
        CO_ALV = O_ALV.       "set_end_of_page

* Calling the top of page method
    CALL METHOD SET_TOP_OF_PAGE
      CHANGING
        CO_ALV = O_ALV.

* Calling the End of page method
    CALL METHOD SET_END_OF_PAGE
      CHANGING
        CO_ALV = O_ALV.

************************************************************************
* Displaying the ALV
* Here we will call the DISPLAY method to get the output on the screen
************************************************************************
    O_ALV->DISPLAY( ).

 METHOD SET_TOP_OF_PAGE.
    DATA: LO_HEADER TYPE REF TO CL_SALV_FORM_LAYOUT_GRID,
          LO_H_LABEL TYPE REF TO CL_SALV_FORM_LABEL,
          LO_H_FLOW  TYPE REF TO CL_SALV_FORM_LAYOUT_FLOW.

========================================================================
Reuse_ALV_GRID:
ALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
      EXPORTING
        i_callback_program          = sy-repid
        i_callback_top_of_page      = 'TOP-OF-PAGE' "see FORM
        i_callback_html_end_of_list = 'END_OF_LIST_HTML' "see FORM
*       is_layout                   = gd_layout
        it_fieldcat                 = li_fcat[]
        i_save                      = 'X'
      TABLES
        t_outtab                    = li_mara
      EXCEPTIONS
        program_error               = 1
        OTHERS                      = 2.
========================================================================
SPILIT Container :

1. Create a custom container for  cl_gui_custom_container.
2. Create O_DD_DOC for CL_DD_DOCUMENT.
3. Create split container for CL_GUI_SPLITTER_CONTAINER for 2 rows and 1 column.
4. create 2 containers for CL_GUI_CONTAINER.
5. Assign first part of ( row 1 ) to container 1.
6. Assign part 2 to container 2.
7. Create a grid for container 2 for CL_GUI_ALV_GRID.
8. Then create a local class and method for TOP_OF_PAGE event of grid.
9. do set handler and rise event,
10. ADD_TEXT, ADD_PICTURE, ADD_GAP, etc. ADD_TEXT is used to add the text and also you can specify the color,font size,font type.

SP ABAP : Performance Tuning

What tools can be used to help with performance tuning?

1. ST05 : this is used to trace performance of the program. it trace SQL performance and mainly used to trace the performance of the select statements used in the program.
2. SAT : used to measure the application performance. it analyse the runtime performance of the program.
3. ST12 : this is combination of ST05 and SAT transactions.
4. EPC (Tcode SLIN) and CI (Tcode SCI ) tools.

What are the steps to optimize the ABAP Code?

http://wiki.scn.sap.com/wiki/display/ABAP/ABAP+Performance+and+Tuning

1. DATABASE
   1. Use WHERE clause in your SELECT statement to restrict the volume of data retrieved.  Very important !!
   2. Design your Query to Use as much index fields as possible in your WHERE statement
   3. Use INNER (or OUTER under some circumstances) JOIN in your SELECT statement to retrieve the matching records at one shot
   4. Avoid using nested SELECT statement and SELECT within LOOPs, better use JOINs or FOR ALL ENTRIES. Use FOR ALL ENTRIES when  the internal table is already there or the end of some processing. Try JOINs if the SELECT are right behind each other
   5. Avoid using INTO CORRESPONDING FIELDS OF TABLE during buffered access. Otherwise use the most appropriate for the program.
   6. Avoid using SELECT * and Select only the required fields from the table.
   7. Avoid using ORDER BY in SELECT statements if it differs from used index  (instead, sort the resulting internal table), because this may add additional work to the database system which is unique, while there may be many ABAP servers
   8. INDEX: Creation of Index for improving performance should not be taken without thought. Index speeds up the performance but at the same time adds two overheads namely; memory and insert/append performance. When INDEX is created, memory is used up for storing the index and index sizes can be quite big on large transaction tables! When inserting new entry in the table, all the index's are updated. More index more time. More the amount of data, bigger the indices, larger the time for updating all the indices
   9. Avoid Executing an identical Select (same SELECT, same parameter) multiple times in the program. Buffer in your abap code.
   10. Avoid using join statements if adequate standard views exist no performance impact
2. TABLE BUFFER:
   1. Defining a table as buffered (SE11) can help in improving the performance but this has to be used with caution. Buffering of tables leads to data being read from the buffer rather than from table. Buffer sync with table happens periodically, only if something changes which is happen rarely. If this table is a transaction table chances are that the data is changing for a particular selection criteria, therefore application tables are usually not suited for table bufferung. Using table buffering in such cases is not recommended. Use Table Buffering for configuration data and sometimes for Master Data.. 
   2. Avoid using complex Selects on buffered tables-, because SAP may not be able to interpret this request, and may transmit the request to the database- The code inspector tells which commands bypass the buffer
3. Internal tables
1. Use HASHED tables where-ever possible. Otherwise SORTED tables. STANDARD tables should be the last choice.
2. Use assign instead of into in LOOPs for table types with large work areas, if the data is being modified.
3. When in doubt call transaction SE30/SAT and check your code.
4. If you must use a STANDARD table and you are using a READ, sort the table appropriately and use the addition BINARY SEARCH to speed up the search. 
4. 
   
5. http://wiki.scn.sap.com/wiki/display/ABAP/ABAP+Performance+and+Tuning
6. Use SLIN and code inspector tools.
7. 
   

SAP ABAP : SD Brief

SD Flow:

INQUIRY->QUOTATION->SALE ORDER->Delivery->SHIPPING->BILLING-

1. Customer's Inquiry 
2. Customer request a quotation - created referring inquiry 
3. Sales Order creation - created referring quotation.(  when customer placed an order )
4. Shipping - Ship the goods to customer
5. delivery
6. Billing/Invoicing
7. Post goods Issue

Transaction Codes:

1. Inquiry : VA11/VA12/VA13
2. Quotation : VA21/VA22/VA23
3. Sales Order : VA01/VA02/VA03 - VBAP VBAK
4. Delivery : VL01N/VL02N/Vl03N - LIKP LIPS
5. Shippment :  VT01/VT02/VT03 - VTTK VTTP
6. Billing  : VF01/VF02/VF03 : VBRK VBRP
7. Invoice : VF21 : VBRK VBRP

SD Master Data : 

1. Condition Master data 
• Pricing data
• Rebate data
• output master data
2. Customer master data XO01/XO02/XO03
3. Material master data  
4. CUST/MAT Info record  VD51
•  mapping of customer name of material to sap name of material.
5. Output master master data (Optional) 

========================================================================

Below is the standard sales and distribution(SD) document flow in SAP .
VBFA is the document flow table

INQUIRY

VA11 is the T-code for inquiry and related tables are VBAK, VBAP.Once inquiry is done customer requests quotation.

QUOTATION

T-code for quotation in VA21, tables are VBAK, VBAP.After quotation flow goes for purchase order.

PURCHASE ORDER

Purchase order t-code is ME21N, related tables are EKKO, EKPO.Based on purchase order sales order will be created.

SALES ORDER

Sales order t-code is VA01, related tables are VBAK, VBAP. Once sales order is created, delivery will be done.

DELIVERY

T-code for delivery order is VL01N, tables are LIKP, LIPS. Next the goods should be dlivered through shipping

SHIPPING

Shipping t-code is VT01, related tables are VTTK, VTTP.Once goods are shipped, go for billing.

BILLING

Billing t-code is VF01, tables are VBRK,VBRP. Every bill has invoice...next provide invoice.

INVOICE

Invoice t-code is VF21, related tables are VBRK, VBRP.Invoice end of sales flow.

=================================================================================

Enhancement Scenario:

• Addition of tab , Item Level : VF01 SD Invoice
• http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=235803375
• Step 1 : Got to SE11 table VBRP
• Step 2 : Add a Z structure to this table with one field Zadd for example.
• Step 3 : Create a Z program and write code to that program.
• Step 4 : add layout in the screen of this Z program. use structure field.
• Step 5 : Go to SE80 and give th eprogram name of the VF01 Transaction. (SAPMV60A)
• Step 6 : Find enhancement point and implement it with following logic:
• Implement CUST_ITEM_ACTIVATE 

=================================================================================

VOFM : 

• VOFM routines are ABAP code written in Forms.
• VOFM provides the user with the benefit of choosing from one of the standard delivered by SAP or writing their own.
• VOFM basically is for the implementation team and not for the end user.
• Copying Requirements : This is provided by SAP to support SD and logistics requirements.
• In each area of VOFM, SAP delivers routines using the name space from 1 to 599.
• SAP customers can create their own VOFM routines using the name space from 600 to 999.
• New VOFM routines created at a customer site are not overwritten by a software upgrade.
•  http://www.newtosap.info/2014/01/vofm-routinesa-short-guide.html
• VOFM routines can be used to propose/alter the business process and it can be triggered for particular condition. Ex: Pricing condition ZCIL which will trigger the routine whenever it’s used.
• There are various categories in VOFM like Data Transfer, Requirements, Formulae’s etc. Depending upon the category, the routine or exit will be called. Ex: any routine done in Formula’s category will be triggered during the computation of formula of a particular pricing condition. One has to choose the correct category and create a new routine.
• V/08 for assigning routine number to the required pricing procedure.
• http://www.saptechsolutions.com/pdf/InsideVOFM.pdf

=====================================================================

Condition Record: 

• The following new transactions are offered:
• Create conditions (transaction VK31)
• Create conditions with reference (transaction VK34)
• Change conditions (VK32)
• Display conditions (VK33)

========================================================================Enterprise structure in SD : 

1. Client  - TATA
2. Company Code - TCS  
3. Sales Area :
• Sales Organisation (Delhi) 
• Distribution channel (online, retail store)
• Division 
• 
4. Plant
5. Shipping Point 
6. Loading Point 

Element of SD Org Structure:

• Sales Organization
• Distribution Channel
• Division
• Sales Office
• Sales Group
• Internal structure: 
• Sales Office
• Sales Group
• Sales Person 

========================================================================

Shipment Process in SAP SD : ( http://scn.sap.com/docs/DOC-45032 )

1. Creation of Sales Order - VA01

2. Creation of Outbound Delivery - VL01N

Shipment process will start form here

 3. Creation of Condition Record for Forwarding Agent, : VK11

• Give condition type (we can create them by copy standard)
• Give the service agent and Tf zone point of dep.
• give the Amount unit and save it .

Service Agent used to calculate net amount in the Shipment cost doc.

 4. Creation of Shipment Document : VT01N

(Note- Shipment document we can create with reference to outbound delivery before PGI or after PGI)

• A shipment document will be created against one or more delivery.

 5. Creation of Shipment Cost Document VI01

   A) PO and service entry sheet will be created automatically by the system.

 6. Enter Vendor’s Invoice (Invoice receipt and verification). MIRO
======================================================================== 

SAP ABAP MACRO

Syntax : 

define Macro1.
....&1... &2...
end-of-definition.

Only used in local program.
Mainly abbreviation for some line of codes in a program.
we cannot debug so we should avoid using macros.

SAP ABAP : Control break events

These events are used inside the loops in ABAP program. There are 5 such events available in ABAP:

1. AT FIRST - ENDAT
• Will trigger at the first run of the loop.
2. AT NEW - ENDAT
• Will Trigger when new value for the applied field.
3. AT END OF - ENDAT
• will trigger for the last occurrence of the same value in the applied field.
4. AT LAST - ENDAT
• Will Trigger withe the last run of the loop,
5. ON CHANGE OF
• Trigger every time change in the value of applied filed. can also be used outside loop.

We must use a temporary workarea to display values in the 3 (2,3,5) control events. otherwise we get values like ***.