VBFA

Former Member — Fri, 01 Feb 2008 16:38:22 GMT

hi all,.

please tell me the correct flow of vbfa and how to use it in delivery note.

urgent

points will be rewarded

Re: VBFA

Former Member — Fri, 01 Feb 2008 16:46:03 GMT

GOOD

Sales

Inquiry - A customer’s request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.

Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.

Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.

The sales area that accepts the inquiry is responsible for completing the agreement.

Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.

b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).

c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.

Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.

Sales Order Management Transactions

SALES ORDER PROCESSING

Creating Sales Order - VA01

Maintaining a Sales Order - VA02

Displaying a Sales Order - VA03

Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1

Display List of RMAs by Customer - VA05

Confirm RMA Goods Receipt - VL02

Generate list of open return orders for deletion - VA05

Display Customer returns eligibility - MCSI

Removing a Billing Block (Approving Credit/Debit Requests) - V.23

PRICING MASTER DATA

Create Pricing - VK11

Creating a Sales Deal - VB21

Maintaining a Sales Deal - VB22

Displaying a Sales Deal - VB23

Maintaining Prices - VK12

Displaying Prices - VK13

MATERIAL MASTER DATA

Creating Material Substitution Master Data - VB11

Maintaining/Deleting Material Substitution Master Data - VB12

Displaying Material Substitution Master Data - VB13

Creating a Bundled Master - MM01

Creating a Sales BOM - CS01

Maintaining a Sales BOM - CS02

Displaying a Sales BOM - CS03

CUSTOMER MASTER DATA

Creating Partner Records - XD01

Maintaining Customer Master Data - XD02

Displaying Customer Master Data - XD03

Deactivating a Partner - VD06

CUSTOMER CREDIT INFO

Creating/Maintaining New Customer Credit Information - FD32

Displaying Customer Credit Information - FD33

Blocking or Unblocking a Customer - VD05

SHIPPING

Creating a Delivery - VL01N

Displaying a Delivery - VL03N

Changing a Delivery - VL02N

Shipment Inquiry / Display - VT03

Adjusting Transfer Order - Confirmation Quantity - LT12

Collectively Confirm Transfer Order - LT25

Batch Shipment Confirmation - VL19

PGI Reversal Cancellation - VL09

Creating Service Provider/Carrier Master Data - XK01

Maintaining Serive Provider/Carrier Master Data - XK02

Displaying Service Provider/Carrier Master Data - XK03

Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02

IDoc Inquiry - WE02 / WE05

BILLING

Invoicing a Customer Shipment - VF01

Reprinting an Invoice - VF31

Releasing a Sales Order for Billing - V.23

Creating an Invoice by Using the Billing Due List - VF04

Checking Open Billing Documents - VF05

Create Credit/Debit Memo - FB01

SD tables

Sales Order - Customer gives a Purchase order to the company agaionst which a Sales order will be raised to Customer in SAP.

VBAK: Sales Document(Header Data) (VBELN)

VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)

Enquiry, Quotation, Sales Order are differentiated based on Doc.

Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,

for Quotation 'B' & for Order it is 'C'.)

Delivery(Picking, Packing, Post Goods Issue and Shipment)->

Company sends the material after picking it from Godown and Packing it in a Handling Unit(box) and Issues the goods

LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)

LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)

(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)

Billing - Also company bills to the customer for those deliveries

And in FI against this billing Accounting doc is created.

VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)

VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)

(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)

Apart from these tables there are lot of other tables which starts with ‘V’, but we use the following tables frequently.

thanks

mrutyun^

Re: VBFA

Former Member — Fri, 01 Feb 2008 16:47:14 GMT

u can get subsequent and preceeding documents using this table .

use the following in the vffa table

vbelv = vbeln

vbtype_n = 'R' .

Re: VBFA

Former Member — Fri, 01 Feb 2008 16:53:09 GMT

what are subsequent and preceding documents

Re: VBFA

Former Member — Fri, 01 Feb 2008 17:07:33 GMT

VBFA is the table where the document flow is stored. This table is VERY usefull. Imagine that you have a Sales Order and you want to know which deliveries it's realted to. You go to VBFA with VBELV (Preceding document) = SALES ORDER and VBTYP_N (Type of subsecuent document) = 'J'. The result are the deliveries (VBELN) related to that sales document.

Here is stored a lot of document relationships, not only the one I've mentioned, check field VBTYP_N for more detail. The use of this table is that if you need to go backwards in the document flow, you just check the content of the related document fields (LIPS-VGBEL in our example), but when going forewards, you would need to change the sales order to store the delivery number and furthermore, more than one delivery could be related to the sales order, hence the need of this table.

Last but not least, remember that this table is for going FORWARDS in the document flow. Never us it to go backwards, because it has low performance (the table is not indexed in that way). You should check the reference fields as I said before.

regards

kushagra

topic VBFA in Application Development and Automation Discussions

VBFA

Re: VBFA

Re: VBFA

Re: VBFA

Re: VBFA