The link between SD and MM :-
1. When you create sales order in SD, all the details of the items are copied from Material master of MM.
2. MRP and availibility check related data is also taken from MM although you control this data in SD also.
3. While you create inbound/outbound delivery with reference to a sales order,the shipping point determination takes place with the help of the loading group, plant data, shipping conditions etc. This also refers to Material Master.
4. The material which you are entering in a sales order must be extended to the sales area of your sales order/customer otherwise you cannot transact with this material.
There are many such links between SD and MM.
Now the link between SD and FI :-
1. Whenever you create a delivery with reference to a sales order, goods movement takes place in the bacgground. eg. In case of standard sales order, you create an outbound goods delivery to the customer.

Here movement 601 takes place. This movement is configured in MM. Also, this movement hits some G/L account in FI. Every such movement of good s hits some G/L account.
2. The accounts posting in FI is done with reference to the billing documents (invoice, debit note, credit note etc) created in SD. Thus this is a link between SD and FI
3. Tax determination: In case of a tax determination also, there is a direct link between SD and MM
SD Integration points with other modules
SD module is highly integrated with the other modules in SAP.
Sales Order –

Integration Points Module

?Availability Check – MM

?Credit Check – FI

?Costing – CO/ MM

?Tax Determination – FI

?Transfer of Requirements – PP/ MM
Delivery & Goods Issue –

Integration Points Module

?Availability Check – MM

?Credit Check – FI

?Reduces stock – MM

?Reduces Inventory $ – FI/ CO

?Requirement Eliminated – PP/ MM
Billing –

Integration Points Module

?Debit A/R – FI/ CO

?Credit Revenue – FI/ CO

?Updates G/ L – FI/ CO

(Tax, discounts, surcharges, etc.)

?Milestone Billing – PS
Return Delivery & Credit Memo –

Integration Points Module

?Increases Inventory – MM

?Updates G/ L – FI

?Credit Memo – FI

?Adjustment to A/R – FI

?Reduces Revenue – FI
SD Transaction Code Flow:
Inquiry / Document type IN

Tcode for creation VA11,VA12,VA13. tables VBAK,VBAP
Quotation / QT

Tcode for creation VA21,VA22,VA23. tables VBAK,VBAP
Purchase Order PO

Tcode for creation ME21,ME22,ME23. tables EKKO,EKPO.
Sales Order OR

Tcode for creation VA01,VA02,VA03. tables VBAK,VBAP
Delivery LF

Tcode for creation VL01,VL02,VL03. tables LIKP,LIPS
Billing MN

Tcode for creation VF01,VF02,VF03. tables VBRK,VBRP
To create a sales order we need purchase order number and custmer number. Before that, to create a purchase order we need to have material no, vendor no.
To create vendor tcode is

xk01(create), xk02(change) , xk03(display)

Tables are lfa1.
To create custmer tcode is xd01, xd02, xd03.

Table is kna1.
After creating sales order using this no we can create delivery note tcode is vl01.

* VS00 – Master Data;
* VC00 – Sales support;
* VA00 – Sales;
* VL00 – Shipping;
* VF00 – Billing.

* VD01 – Create customer master;
* VD02 – Change customer master;
* VD03 – Display customer master;
* XD01 – Create customer master centrally;
* XD02 – Change customer master centrally;
* XD03 – Display customer master centrally;
* VD04 – Customer account changes;
* VD06 – Customer deletion flag;
* VKM3/VKM4 – Sales documents list.

* MM01 – Create material master;
* MM02 – Change material;
* MM03 – Display material.

* MMBE – Stock Query
* MB52 – Ware house Stock

* VA01 – Create sales order;
* VA02 – Change order;
* VA03 – Display order;
* VA05 – Sales order list.

* ME21N – Purchase Order
* ME51N – Puchase order from Purchase requisition

* MIGO – Goods Movement

* VL01 – Create delivery;
* VL02N – Change delivery document;
* VL04 – Delivery due list;
* VKM5 – Deliveries list;
* Vl09 – Goods issue cancel.
* VL31n- Inbound delivery

* VF02 – Billing document change;
* VF04 – Billing due list;
* VF11 – Billing document cancel.

* CO09 – Material availability overview;
* MMBE – Stock overview.

* VOV4 – Assign Item categories;
* VOV6 – Scheduling line categories;
* VOV8 – Define Sales document.

* VOK0 – Maintain Pricing;
* V/06 – Pricing;
* V/07 – Access sequence;
* V/08 – Maintain pricing procedure;
* OVKP – Pricing procedure determination.

* VK11 – Maintain Condtion records;

* IW21 – Create notification
* IW31 – Create work order
* IE01 – Create Equipment master

* FPE1- Create document
* FPE2- Change document
* FPE3- Display document

* INSOCREATE – Create Insurance object
* INSOCHANGE – Change Insurance object
* INSODISP – Display Insurance object

* MD04 – Stock Requirement

In SE37 Look for GRAPH* and GRAPH_matrix* for other function modules for
graphics.

Examples of functionmodules:

GRAPH_2D
GRAPH_MATRIX

There is also a demoprogram called: REKH0004

This tip has been copied from SearchSap.com
Tip submitted by: Tim Jones

Here is a small addition to a tip from Matthew Billingham on how to locate user exits. Instructions are
relevant to 4.6B but I’m pretty sure I’ve used it in earlier versions. It’s been a while though.

If you goto the SAP Application hierachy (SE81)you can go down into individual modules.

Select the area you are interested. (It should turn yellow).

Choose Information System button.

Select Environment—>Exit Techniques–>Customer Exits—>Enhancements.

You should now belooking at a selection screen with the DEV classes filled in from the Application
hierachy.

If you hit Execute you will get the exits for the selected part of the hierachy!

Have a play around with SE81 / Info system it can be very usefull in finding all sorts of interesting
things!

Above all Enjoy!

This tip has been copied from SearchSap.com
Tip submitted by: Chimou Chim

Direct call of transactions, session handling

/nxxxx This terminates the current transaction, and starts transaction xxxx

/n This terminates the transaction. This generally corresponds to pressing F15 to go back.

/nend This terminates all separate sessions and logs off (corresponds to System – Logoff

/nex This terminates all separate sessions and logs off immediately (without any warning!)

/oxxxx This opens a new session and starts transaction xxxx in This session.

/o This lists existing sessions and allows deletion or opening of a new session.

/i This terminates the current session (corresponds to System End

/i1, /i2,… This terminates the session with the number given.

.xyzw Fast path: ‘xyzw’ refers to the underlined letters in the menus. This type of navigation is
uncommon and is provided more for emergencies (such as a defective mouse).

Batch input. The following commands can be entered in correction mode (‘Process in foreground’ or
‘Display errors only’) when processing a batch input session

/n This terminates the current batch input transaction and characterizes it as

/bdel This deletes the current batch input transaction.

/bend This terminates batch input processing and sets the session to Failed

/bda This switches from Display errors only to Process in foreground

/bde This switches from Process in foreground to Display errors only

ABAP

/h This switches into debugging mode.
/hs This switches into debugging mode and activates the debugging of system functions.

Buffer

WARNING: Resetting buffers can significantly change the performance of the entire system for a
long time. It should therefore only be used where there is a good reason tdso. As of release 3.0B
system administator authorization is required (authorization object (S_ADMI_FCD). The action is
noted in the system log.

/$SYNC This resets all buffers of the application server

/$CUA This resets the CUA buffer of the application server

/$TAB This resets the TABLE buffers of the application server

/$NAM This resets the nametab buffer of the application server

/$DYNP This resets the screen buffer of the application server

/*xxxx starts transaction xxxx and skips the first screen. So, it has the same effect as /nxxxx
followed by ENTER.

=xxxx This entry is still possible for compatibility reasons, but is no longer supported.

%sc Searches character patterns in lists

%pc Downloads lists

%pri Prints lists

  • Transaction code – SMW0
  • X – Binary data for WebRFC application
  • Hit Enter
  • Click Execute
  • Click Settings -> Maintain MIME types
  • Click the Create button
  • Fill in :
    • TYPE : image/gif
    • EXTENSION : .GIF
  • Click Save
  • Click Back to the Binary data for WebRFC
  • Click Create
  • Fill in :
    • Obj. name : ZXXXX.GIF
    • Description : Company Logo
  • Click Import and specify the filename where your GIF file is located. File type is BIN. Finish press the Transfer button.
  • If successful, your logo will be shown in the Binary data for WebRFC.
  • Transaction code SM30 – Table/View – SSM_CUST
  • Click Maintain
  • Click New Entries
  • Name Value to be set
  • START_IMAGE ZXXXX.GIF
  • RESIZE_IMAGE NO
  • Logoff and Login again
  • Bugün 22 Ocak 2007 Pazartesi.

     Yaklaşık 2.5 yıldır devam eden ABAP yazılım kariyerimi bugün itibari ile analiz tarafında devam ettireceğim. Temel ABAP bilgisine sahip bir modül danışmanı olarak olaylara biraz daha teknik bakabileceğimi biliyorum.

     Modül kısmında beklentilerim, aşırı detaycı olan teknik yönümün biraz daha müşteri yaklaşımlı olarak eğitilmesi. Böylece hem teknik hem de müşteri yönlü düşünebilme yetilerini kazanan bir kariyer sahibi olacağım.

    Umarım bu departman benim için hayırlara vesile olur.

    Categories

    • No categories