I need vbeln(sales document no),vbeln1 (subsequent sd doc) in alv report.

I am using below structure for sd alv reports.
        BEGIN OF st_vbak,
          vbeln TYPE vbak-vbeln,
          erdat TYPE vbak-erdat,
        END OF st_vbak,
        BEGIN OF st_vbfa,
          vbelv TYPE vbfa-vbelv,
          vbeln1 TYPE vbfa-vbeln,
        END OF st_vbfa,
       BEGIN OF st_final,
         vbeln TYPE vbak-vbeln,
         erdat TYPE vbak-erdat,
         vbelv TYPE vbfa-vbelv,
         vbeln1 TYPE vbfa-vbeln,
        END OF st_final.
i need vbeln(sales document no), erdat, vbeln1 (subsequent sd doc) in report output..
i.e. By comparing vbeln -vbak and vbelv-vbfa ,it should show the result.
i need select and loop statemnt...
help plz..
Moderator Message: Stop dumping your Consulting work here without proper effort from your end. You have already been warned many times previously.
Edited by: kishan P on Mar 7, 2012 3:47 PM

Hi,
Please do some research on SDN. Also refer the PDF for SAP Tables Relation.
Regards,
Danish.

Similar Messages

Need to remove space for a field when displayed in ALV Report

Hi,
I have material field of length 18, but the content is only 10 char. I need to remove the extra space when it is displayed on ALV Report.
Is there any option in ALV field catalogue

use statement condense.
condense zmatnr.
also giv output lenth of alv column as 10.

Article number is missing for a sales document in VBAP table compared to BW data.

Hi,
We are loading data from 2LIS_11_VAITM and 2LIS_11_V_SSL to 0SD_O01, when we execute a report based on this DSO we are getting Article number 2224859 (for example) for sales order 573345 (for example) but when we check in VBAP/VA03 for the same sales order/document (573345) we don't have the Article Number.
It is delta load to the DSO from the two datasources and will executed daily once.
Please suggest me any one on this.

All,
Thanks for your replys.
Here are the more details about this.
We are using 3.X flow in BW. (3.x Data sources)
In BW Mapping In ECC
0DOC_NUMBER Sales document -----------> VBELN Sales Document
0MATERIAL Material -----------------------> MATNR Article Number
In VBAP table, I have entered Sales document 573345 and executed then I got so many Article Numbers and Filtered with Article Number 2224859 then got no data.
As I told earlier in BW for the same Sales Document number we have Article Number.
We have start routine.
PROGRAM UPDATE_ROUTINE.
*$*$ begin of global - insert your declaration only below this line *-*
*$*$ end of global - insert your declaration only before this line *-*
* The follow definition is new in the BW3.x
TYPES:
BEGIN OF DATA_PACKAGE_STRUCTURE.
 INCLUDE STRUCTURE /BIC/CS2LIS_11_VAITM.
TYPES:
 RECNO LIKE sy-tabix,
END OF DATA_PACKAGE_STRUCTURE.
DATA:
DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
 WITH HEADER LINE
 WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
FORM startup
TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
 MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
 DATA_PACKAGE STRUCTURE DATA_PACKAGE
USING RECORD_ALL LIKE SY-TABIX
 SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
*$*$ begin of routine - insert your code only below this line *-*
* fill the internal table "MONITOR", to make monitor entries
LOOP AT DATA_PACKAGE.
 IF DATA_PACKAGE-doc_categ NE 'C' AND
 DATA_PACKAGE-doc_categ NE 'I'.
 DELETE DATA_PACKAGE.
 elseif DATA_PACKAGE-recordmode eq 'R'.
 DATA_PACKAGE-recordmode = 'X'.
 modify DATA_PACKAGE.
 ENDIF.
ENDLOOP.
* if abort is not equal zero, the update process will be canceled
ABORT = 0.
*$*$ end of routine - insert your code only before this line *-*
ENDFORM.
I think there is no much more lookups. ( I don't have much knowledge in ABAP)
I have checked in another tables also like VBFA VBAG VBAK, VBKD, VBUK and VBUP but in those tables I don't have Article (MATNR) field.
One more Question.
Can any one tell me how the Queued Delta mechanism will work.
As of now I know that, when ever any changes have been done to the tables this will pickup the changes and move into LBWQ after that RSA7.
My Question is, If some one has forcefully deleted one Article number from the table for a Sales Order then this Queued delta will pick that also?
Please let me know If you need any more details

Report to show the followup sales documents and items

Sales had executed many sales quotations with customers over a period of time.
Now the Sales Staff wanted to know how many sales documents and what/how many sales items are being purchased by the customer with respect to the quotation.
Is there a report that list out the sales documents and items created w/respect to a particular quotation instead of looking at the document flow which is difficult to diagnose.
Thanks

hello, friend.
you can try table VBFA, where you can see sales documents and their subsequent documents.
for a general listing of quotations, use tcode VA25.
regards.

How can I get the correct Ship To (KNVP-KUNNR2) for a Sales Document?

I am trying to generate a report that will (among other things) display the Ship To ID and Name for a given Sales Document. I know the following information:
VBAK-VBELN - Sales Document
VBAK-VKORG - Sales Org
VBAK-VTWEG - Distribution Channel
VBAK-SPART - Division
VBAK-KUNNR - Sold To Party
I know that the table KNVP will return a list of Ship-To Customer numbers (KUNNR2) for a Sold-To Customer (VBAK-KUNNR) if I also filter by VKORG, VTWEG, and SPART (using SE16N). What I don't know is which one of the returned values is being used in a particular Sales Document. The customer in question has 29 Ship-To locations. How do I find out which Partner Counter (KNVP-PARZA) the Sales Document uses? I don't know where that value would come from. Once I can get the correct Ship-To Customer Number, I should be able to search the table KNA1 by WHERE KUNNR = KNVP-KUNNR2 and return KNA1-NAME1 for the Name of the Ship-To location.

For a sales document? Use VBPA with PARVW = 'WE'. Also, use the ADRDA field to determine whether the address on the document has been manually changed. In any case, you can use one of the many address management functions or just ADRC directly to get the name, address, etc., using the ADRNR field from VBPA or if the address is from the customer master, KNA1.

Sales Document Filed in F-37 and F-29 T.codes

Hi All
My client is using SAP R/3 4.6C Version. When i'm posting a document in F-37 or F-29 (Customer Down Payment Request or Customer Down payments) I want to link the down payment to the Sales Document. For that I need the Sales Document Field and the Sales Document Item field in that transaction code. I need to add that field in that T.Code. Please advice. I have a doubt that it comes from the Subscreen for Coding blocks. I want to know how to select the needed subscreen for coding blocks. Please let me know ASAP
Regards
Rajaram

Hi
I know that but the Sales Document filed is not there in that T.code. Thats the problem.
Regards
Rajaram

Need to calculate Document amount based on below conditions

Hi Everybody
Here I need to calculate Document amount based on below conditions in the report iam having all the fields.
1)     If the Net Due Date is one or up to tens days less than the document date on any open AP item
2)     If the Net Due Date is "equal to" or "less than" the next month end date on any open AP item
3)     If the Net Due Date is "one day more than" the next month end date on any open AP item
4)     If the "GR posting date" + "payment in days (no of days)" is "one day more than" the next month end date
5)     If the Net Due Date of any open AP item is in Jan., FebDec, place the document amount in Jan, Feb...Dec month
6)     If "Payment date > net due date" from 11 to 30 days add amount
Pls write ur comments if any userexits pls forward to my id
[email protected]
Thanks in Advance
Chaitanya

you can have parameters to pass the points and you can use this inside query to filter and return the required data from query. You can then use this dataset inside chart and plot the points.
http://www.grapefruitmoon.net/ssrs-2008-using-the-top-filter-in-a-chart/
http://blogs.msdn.com/b/florianmader/archive/2013/08/10/sorting-a-chart-by-values-in-ssrs.aspx
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Need Help in Interactive ALV Report

Hi guru's,
I need sample code of Interactive ALV when on selecting an particular field, it should open an another ALV windows or pop-up window. Please help me and points will be rewarded for the right code.
Regards
Rajiv Christopher

hi,
may b it will b helpful 2 u.
INTERACTIVE ALV
REPORT Z50651_ALV_INTERACTIVE MESSAGE-ID ZMSG_50651
LINE-SIZE 100
LINE-COUNT 60
NO STANDARD PAGE HEADING.
******************TABLES DECLARATION*****************
TABLES : VBAP,MARA.
*****************TYPE POOLS**************************
TYPE-POOLS : SLIS.
****************INTERNAL TABLES**********************
DATA : BEGIN OF IT_VBAP OCCURS 0,
VBELN LIKE VBAP-VBELN, "SALES DOCUMENT
POSNR LIKE VBAP-POSNR, "SALES DOCUMENT ITEM
MATNR LIKE VBAP-MATNR, "MATERIAL NUMBER
END OF IT_VBAP.
****************TEMPORARY VARIABLES******************
DATA : V_VBELN LIKE VBAP-VBELN."SALES DOCUMENT
DATA : V_MTART LIKE MARA-MTART. "MATERIAL TYPE
*****************FIELD CATALOG***********************
DATA : IT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
****************LAYOUT*******************************
DATA : WA_LAYOUT TYPE SLIS_LAYOUT_ALV.
***************VARIANT*******************************
DATA : G_VARIANT LIKE DISVARIANT.
****************SAVE*********************************
DATA : G_SAVE(1) TYPE C.
*****************EVENTS******************************
DATA : XS_EVENTS TYPE SLIS_ALV_EVENT,
G_EVENTS TYPE SLIS_T_EVENT.
******************PF STATUS**************************
DATA : PF_STATUS TYPE SLIS_FORMNAME VALUE 'SET_PF_STATUS'.
******************USER COMMAND************************
DATA : USER_COMMAND TYPE SLIS_FORMNAME VALUE 'SET_USER_COMMAND',
R_UCOMM LIKE SY-UCOMM.
****************SELECTION SCREEN************************
SELECT-OPTIONS : S_VBELN FOR VBAP-VBELN.
***************AT SELECTION SCREEN*********************
AT SELECTION-SCREEN.
PERFORM VALIDATE.
**************START-OF-SELECTION**************************
START-OF-SELECTION.
PERFORM GET_DETAILS.
PERFORM FIELDCAT.
PERFORM LAYOUT.
PERFORM VARIANT.
PERFORM SAVE.
PERFORM EVENTS.
PERFORM ALV_DISPLAY.
*********************FORMS*******************************************
*& Form validate
text
--> p1 text
<-- p2 text
FORM VALIDATE .
SELECT SINGLE VBELN
FROM VBAP
INTO V_VBELN
WHERE VBELN IN S_VBELN.
IF SY-SUBRC <> 0.
MESSAGE E000 WITH 'enter valid vbeln'.
ENDIF.
ENDFORM. " validate
*& Form get_details
text
--> p1 text
<-- p2 text
FORM GET_DETAILS .
SELECT VBELN
POSNR
MATNR
FROM VBAP
INTO TABLE IT_VBAP
WHERE VBELN IN S_VBELN.
IF SY-SUBRC <> 0.
MESSAGE E000 WITH 'no details found'.
ENDIF.
ENDFORM. " get_details
*& Form fieldcat
text
--> p1 text
<-- p2 text
FORM FIELDCAT .
WA_FIELDCAT-TABNAME = 'IT_VBAP'.
WA_FIELDCAT-FIELDNAME = 'VBELN'.
WA_FIELDCAT-OUTPUTLEN = 10.
WA_FIELDCAT-SELTEXT_L = 'SALES DOC'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-TABNAME = 'IT_VBAP'.
WA_FIELDCAT-FIELDNAME = 'POSNR'.
WA_FIELDCAT-OUTPUTLEN = 6.
WA_FIELDCAT-SELTEXT_L = 'ITEM'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
WA_FIELDCAT-TABNAME = 'IT_VBAP'.
WA_FIELDCAT-FIELDNAME = 'MATNR'.
WA_FIELDCAT-OUTPUTLEN = 18.
WA_FIELDCAT-SELTEXT_L = 'MATERIAL NO'.
APPEND WA_FIELDCAT TO IT_FIELDCAT.
CLEAR WA_FIELDCAT.
ENDFORM. " fieldcat
*& Form LAYOUT
text
--> p1 text
<-- p2 text
FORM LAYOUT .
WA_LAYOUT-ZEBRA = 'X'.
ENDFORM. " LAYOUT
*& Form VARIANT
text
--> p1 text
<-- p2 text
FORM VARIANT .
CLEAR G_VARIANT.
G_VARIANT-REPORT = SY-REPID.
ENDFORM. " VARIANT
*& Form SAVE
text
--> p1 text
<-- p2 text
FORM SAVE .
CLEAR G_SAVE.
G_SAVE = 'A'.
ENDFORM. " SAVE
*& Form EVENTS
text
--> p1 text
<-- p2 text
FORM EVENTS .
CLEAR XS_EVENTS.
XS_EVENTS-NAME = SLIS_EV_TOP_OF_PAGE.
XS_EVENTS-FORM = 'TOP_OF_PAGE'.
APPEND XS_EVENTS TO G_EVENTS.
ENDFORM. " EVENTS
*& Form TOP_OF_PAGE
text
FORM TOP_OF_PAGE.
WRITE :/ ' INTELLI GROUP'.
ENDFORM. "TOP_OF_PAGE
*& Form ALV_DISPLAY
text
--> p1 text
<-- p2 text
FORM ALV_DISPLAY .
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE = ' '
I_CALLBACK_PROGRAM = SY-REPID
I_CALLBACK_PF_STATUS_SET = PF_STATUS
I_CALLBACK_USER_COMMAND = USER_COMMAND
I_STRUCTURE_NAME =
IS_LAYOUT = WA_LAYOUT
IT_FIELDCAT = IT_FIELDCAT
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = G_SAVE
IS_VARIANT = G_VARIANT
IT_EVENTS = G_EVENTS
IT_EVENT_EXIT =
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
TABLES
T_OUTTAB = IT_VBAP
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
IF SY-SUBRC 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " ALV_DISPLAY
*& Form SET_PF_STATUS
text
FORM SET_PF_STATUS USING EXTAB TYPE SLIS_T_EXTAB.
SET PF-STATUS 'Z50651_PFSTATUS' EXCLUDING EXTAB.
ENDFORM. "SET_PF_STATUS
*& Form SET_USER_COMMAND
text
FORM SET_USER_COMMAND USING R_UCOMM
RS_SELFIELD TYPE SLIS_SELFIELD.
CASE R_UCOMM.
WHEN 'DC'.
READ TABLE IT_VBAP INDEX RS_SELFIELD-TABINDEX.
IF SY-SUBRC = 0.
SELECT SINGLE MTART
FROM MARA
INTO V_MTART
WHERE MATNR = IT_VBAP-MATNR.
IF SY-SUBRC 0.
MESSAGE E000 WITH 'NO MATERIAL DESCRIPTION FOR SELECTED MATERIAL NO'.
ELSE.
WRITE :/ 'MATERIAL NO :',IT_VBAP-MATNR.
WRITE :/ 'MATERIAL TYPE :' , V_MTART.
ENDIF.
ENDIF.
WHEN 'BACK'.
LEAVE TO SCREEN 0.
WHEN 'EXIT'.
LEAVE TO SCREEN 0.
WHEN 'CLOSE'.
CALL TRANSACTION 'SE38'.
ENDCASE.
ENDFORM. "SET_USER_COMMAND
Reward if useful...

Documents on ALV Reporting

Hi,
Could you please send me the detailed document links and PDFs if you have any on ALV reporting to my email - [email protected]
Thanks,
Bobby.

Here you go ...
http://www.geocities.com/mpioud/Abap_programs.html
http://www.geocities.com/mpioud/Z_DEMO_ALV_REFRESH_BUTTON.html
http://www.sap-img.com/fu037.htm
/people/ravikumar.allampallam/blog/2005/06/01/alv-reporting-using-controls--part-i
/people/ravikumar.allampallam/blog/2005/06/01/alv-reporting-using-controls-control-layouts--part-ii
/people/thomas.jung3/blog/2005/10/26/alv-om-template-program
/people/sap.user72/blog/2005/09/14/a-new-approach-to-alv-programming
/people/thomas.jung3/blog/2005/09/08/oo-abap-dynpro-programming
/people/ravikumar.allampallam/blog/2005/05/31/expand-the-list-of-columns-in-a-report-dynamically
/people/subramanian.venkateswaran2/blog/2004/11/19/dynamic-internal-table
/people/ravikumar.allampallam/blog/2005/12/05/need-a-way-to-change-appearance-of-a-standard-existing-alv-report
Apart from these search for articles on ALV, you will get a quite a few.
Regards,
Ravi
Note : Please mark the helpful answers

What is the need of creating partner functions for sales document type.

Hi SAP (SD-GURUS),
Actually we create partner functions before creating customer ex: sold to party, ship to party, bill to party, and payer.
These partner functions are going to be copied into sales order while processing sales order.
Again what is the need of creating partner functions for sales document type.
Thanks&Regards
sreenivas peruru

There are some Partners you could enter at Sales ORder Level. E.g. Sales Person, Employee Responsible, Forwarding Agent, Broker, etc.
Thus these partner Determination need to be carried out at Sales Order Level & not at Customer Master level.
So we have to configure partner Determination for various levels e.g. Customer Master, Sales Order, Delivery level etc...
Hope this helps...
THanks,
Jignesh Mehta

Sales document created from CRM 4.0 needs to be updated from ECC 6.0

Hello experts,
When I create one sales document from CRM 4.0 this document is moved to ECC 6.0. But updating sales document from ECC 6.0 I receive message
 "Process the original document in the CRM system"
and updates are not moved to CRM.
How could I avoid this ?
Usually I need update some fields from ECC 6.0 and move the information to CRM.
Regards
Juan

Hi Juan,
Please check the Note 541113 - Data exchange scenarios for orders (CRM-R/3) in which as per your requirement its the scenario Z i.e you want some data to flow from ECC to CRM for which below are the settings that needs to be done to make it effective.
Activation of the scenario in table CRMPAROLTP of the R/3 plug-in:
PARNAME: CRM_SCENARIO
PARNAME2: UPLOAD_ORDER
PARVAL1: Z
Go to SM30 and give the table name and put in the above values.
And if you want to make amutual change situation then proceed as follows:
Settings in the CRM Server: Table SMOFPARSFA
 Key: R3A_SALES
 Parameter Name 1: INT_CHANGE_ORDER
 Parameter Name 2: <sales document type> , for example TA
 Parameter Value 1: Z
Settings in the R/3 system: table CRMPAROLTP
 Parameter Name: CRM_SCENARIO
 Parameter Name 2: INT_CHANGE_ORDER
 Parameter Name 3: <sales document type> , for example TA
 Parameter Value: Z
Hope it helps.
Regards
Sidd

Need a BAPI to modify sales document (Inquiry) header conditions

I need a bapi to modify header conditions on an Inquiry sales document. BAPI_CUSTOMERINQUIRY_CHANGE has the appropriate condition and conditionx tables. However, according to the documentation: "Although the BAPI interface is supplied for the condition to be changed, the system does not return the required result and/or the pricing result is inconsistent. Currently, the change of condition lines in existing documents via the BAPIs provided by SAP is not implemented."
Thanks
Leo

Vinod
Thanks. I tried that bapi yesterday but, as you say, it's difficult to implement. I haven't been able to get it to work yet.
Leo

Text Determination Sales document to sales document

Hi Friends,
We are configuring text determination sales document to sales document (ZOR to ZLR).
We have done following configuration:
1. text type - Z122 ( invoice text header)
2.) test determination procedure Z1. In text determination procedure Z1 is copy button is enabled. and access seguence 9122 is assigned.
3. text determination Z1 is assigened to text type Z122.
4.) text determination is assigned to document type - ZOR.
let me know what configruation we are missing here.
While creating sales order we are giving some description in header text invoice header but the same is not copied to subsequent document ZLR. ( debit memo request).
We are using this in Resource related billing.( RRB).
Document flow is
sales order ( zor)-internal order ( ko01)- Accounting document( fb01)- Resource relating billing doc ( DP91) we generate debit memo request from DP91.
We need the invoice text entered in sales order (va01) to copied in debit memo request ( ZLR.)
We need this at both header and item level.
kindly suggest.

Hi,
Which text determination and text types assigned to ZLR?
If you maintain- same text type - you can copy
Thanks
Chidambaram

Sales scheduling agreements and subsequent sales orders in MD04

We would like to use sales scheduling agreements. For planification purposes, we need that forecast delivery schedule quantities in the agreement, appear in MD04 transaction, so corresponding schedule line type has flag "Transfer of requirements" active. In customizing for the agreement type, subsequent documents are sales orders, not deliveries, as we need always to have a sales order. We need that when creating subsequent sales order by reference to the scheduling agreement, quantity required related to the agreement is reduced. Or, at least, when this subsequent sales order is delivered.
Example: In the agreement we can have 1000 KG and 2000 KG as forecast, for different dates. If a sales order of 800 KG is created, then we will get a new line of 800 KG in MD04. Required quantity related to the agreement, should be changed from 1000 to 200.
Another option would be that subsequent sales order and delivery don't appear in MD04 (so requested quantity is not increased) and then, when the goods issue is posted, the available quantity is reduced and also the quantity required related to the agreement. I know how to make that sales order item is not relevant for MD04 using flag "Transfer of requirements" for the sales order schedule item type, but I don't know how to make that delivery doesn't appear.
Edited by: CH Spain on Dec 28, 2007 1:08 PM

Hi
In the given logic include another comment
If zfield value = 01, then allow creation of subsequent document.
If zfield value # 01, then subsequent document creation should not be allowed.
If AUART = Z sales document types then allow creation of subsequent document
If VKORG (Sales organisation) =1000 then allow creation of subsequent document
If VTWEG (Distribution channel) = 01then allow creation of subsequent document
If SPART (Division) = 01then allow creation of subsequent document
It wont affect if you change the copy control requirement routine,but instead of changing the copy control requirement routine
use the user exit at sales order level only.
Regards
Srinath

Explanations on Sales Documents

Can anybody send explanations about sales documents that I have mentioned below?
Inquiry IN
Quotation QT
Free-of-charge delivery FD
Standard sales order OR
Cash sale BV
Rush order SO
Quantity contract CQ
Maintenance contract WV
Rental contract MV
Scheduling agreement DS
Credit memo request CR
Debit memo request DR
Subsequent delivery, free-of-charge SD
Returns RE

hi
==============================
can also refer to the link below for more info on SD ..
SD Process Flow
==============================
SD FLOW:
Sales
Inquiry - A customers 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
A/R
Controlling Total Debit/Credit bkgs - F.03
Generate FI Account balance - F.08
Generate Month-to-date Inv. register - F.02
Process payments - FBZ1
Rqst Individual Customer Corresp. - FB12
Generate Customer Correspondence - F.61
Enter Batch totals under Control ttl - FB07
Display G/L Acct. totals - FBL3N
Reverse Posted Amounts - FB08
Customer Refunds - FBL6
Customer Refund to other than Payer - FB05
Clearing Debit/Credit on Cust. acct. - FB1D
Customer Balance in Local Currency - F.23
G/L Account Balance Report - F.08
Create Invoice - legal entity adjust - FB01
Generate Cust. Acct. statements - F.27
Generate Dunning Letters - F150
Generate Billing Due List - VF04
Generate Blocked Billing Doc list - VFX3
Inq. via Credit Release Screen - VKM1
List orders by partner - VA05
Past Due invoices by customer - FD11
Check number info by G/L account - FBL3N
Display customer Line items - FBL5N
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
he configuration differs from scenario to scenario & requirement of the client.
Interesting &important link to learn much more about configuration & business process is as under:
Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on.
====
Cash Sale & Rush Order
Cash Sales and Rush Orders
====
Contracts
General Contract Processing
http://help.sap.com/erp2005_ehp_02/helpdata/en/5e/69a1228f6211d2a9f60000e8a6f09e/frameset.htm
Renewing Contracts
http://help.sap.com/erp2005_ehp_02/helpdata/en/2c/275c9c456a11d189440000e829fbbd/frameset.htm
Subsequent Rental
http://help.sap.com/erp2005_ehp_02/helpdata/en/42/c820c5f8191377e10000000a1553f7/frameset.htm
Real Estate Contract
http://help.sap.com/erp2005_ehp_02/helpdata/en/8d/fb783b05efdb18e10000000a114084/frameset.htm
Value Contract
http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fd7a545a11d1a7020000e829fd11/frameset.htm
Creating and Sending Complaint Notifications
http://help.sap.com/erp2005_ehp_02/helpdata/en/2a/df32f73d7a4bbd8d6e50b32e9227e8/frameset.htm
Use of Value Limits (for Unplanned Services)
http://help.sap.com/erp2005_ehp_02/helpdata/en/c3/72cd0755cd11d189660000e8323c4f/frameset.htm
====
Quantity Contract
http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fd60545a11d1a7020000e829fd11/frameset.htm
http://help.sap.com/erp2005_ehp_02/helpdata/en/70/23c791419311d2ac100000e829fbfe/frameset.htm
Batch Determination in Quantity COntract
http://help.sap.com/erp2005_ehp_02/helpdata/en/25/283c804f7811d18a150000e816ae6e/frameset.htm
Customer Contracts
http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fd53545a11d1a7020000e829fd11/frameset.htm
Purchase Contract
http://help.sap.com/erp2005_ehp_02/helpdata/en/70/23c6ce419311d2ac100000e829fbfe/frameset.htm
Contract Settlement & Billing
http://help.sap.com/erp2005_ehp_02/helpdata/en/ea/00efa6f94011d2968c006094b92c6a/frameset.htm
====
Service Contract
http://help.sap.com/saphelp_sm40/helpdata/en/8f/b4113a7e31e403e10000000a11402f/frameset.htm
Processing Service Contract
http://help.sap.com/saphelp_46c/helpdata/en/e6/4a8f849e0311d189b70000e829fbbd/content.htm
Service Order Processing
http://help.sap.com/saphelp_crm40/helpdata/en/81/78963ec975667fe10000000a114084/content.htm
Sub Contracting Cycle
(1) You have a material that can be procured externally, and you have maintained BOM with components. Any waste generated and received during subcontracting process can be maintained as component with negative quantity.
(2) You create a subcontracting PO (PO with Item Category L). You can also maintain Purchase Info Record for Subcontract category for material and subcontractor.
(3) You make a transfer posting to issue components for SC PO. Material is sent to subcontractor. As material remains under your ownership, system does not make any value entry. But quantity is shown as "Material Provided to Vendor"
(4) You receive finished material against SC-PO. You also specify components consumed in manufacturing of finished goods. Additionally, if you have negative components in BOM, now you'll also receive subcontracting by-products. There are three events, so three accounting entries are generated:
DR FG Stock/ SC By-Product Stock
CR Change in Stock (FG/ SC By-Product )
(for finished goods received)
DR Subcontracting Charges
CR GR/IR Clg
(for moneys payable to Subcontractor)
DR Consumption (Components)
CR Change in Stock (FG/ SC By-Product )
(material provided to Vendor is now charged to expense)
(5) You do the IV for SC Invoice, and the process is complete.
Process of Subcontract in MM
Sub-contract business process:
You want to buy material from the supplier (processed material/ assembled item) , but for some reason (quality of certain item / price ) you will give some component to vendor .
Vendor shall process the item / use the item provided & supply the final item.
SAP process:
1.Create the finished goods material code.
2.Maintain the BOM for the material.
3.Create PO with item category as "L" .
4.Issue material to vendor with movement type 541
5.Receive the material against the PO with movement type 101.
6.MIRO to account for vendor's invoice for the service charge& material used by him.
Can anybody tell me how a process has to be given to subcontracting?
Suppose, I have 3 operations 1)weaving 2)dyeing 3)cutting & packing
if no 2 process (i.e Dyeing) has to be given to subcontracting, what process should i follow ?
The following process to be followed for subcontracting.
1. Item code(material master) to be created at the stage of before dyeing.
2. Item code(material master) to be created after Dyeing as subcontracted item.(F30)
3. Bill of material to becreated for the material(2) calling for material(1)
4. Inforecord and source list to be created for material(2) with the corresponding vendor
5. PO to be released for material (2)
6.Along with PO the material(1) to be issued to vendor
7.On receipt of material when GR is made the stock with vendor will get updated.
How to Create a Subcontract Order?
To create a subcontract order, proceed as follows:
Enter the material you want to order and the item category for subcontracting (L) in the order item.
Press ENTER to display the screen for component processing.
Enter the components that the vendor requires to manufacture the product.
Please note:
You do not need to enter the date required for the components. This date is proposed by the system when you press ENTER.
It is calculated as follows:
Delivery date of the item - Planned delivery time
If you do not want the quantity of the components to be changed if the order quantity of the end product is altered, set the indicator Fixed quantity (column F).
You can determine whether the components are available on the date required by selecting Edit -> Availability check.
If you entered a bill of material as the material in the subcontract order, the components are created automatically.
If you want to determine the components in the bill of material at a later date (for example, if the bill of material is subsequently changed), choose Item -> Component -> New BOM explosion. The existing components are deleted and redetermined in the bill of material.
Save the purchase order.
When you print the purchase order, the components are printed per order item.
====
Scheduleing AGreements
Creating Schedule Agreements
http://help.sap.com/erp2005_ehp_02/helpdata/en/75/ee0f8155c811d189900000e8322d00/frameset.htm
Controling Scheduling Agrement
http://help.sap.com/erp2005_ehp_02/helpdata/en/93/7439ee546011d1a7020000e829fd11/frameset.htm
Example Data
http://help.sap.com/erp2005_ehp_02/helpdata/en/8a/815cc3b36211d188e70000e8216438/frameset.htm
Mass Maintenance of Scheduleing Agreements
http://help.sap.com/erp2005_ehp_02/helpdata/en/1a/8b4bbecdd74536acd4e970faaf6e2d/frameset.htm
Initial Data Transfer
http://help.sap.com/erp2005_ehp_02/helpdata/en/49/87c646f4a311d1955100a0c9306667/frameset.htm
Analysis & Copying of Scheduling Agreements
http://help.sap.com/erp2005_ehp_02/helpdata/en/45/f9a69036035f4be10000000a114a6b/frameset.htm
Processing Scheduling Agrements
http://help.sap.com/erp2005_ehp_02/helpdata/en/bd/1850f298a911d194fc00a0c9306667/frameset.htm
Scheduling Agreements for Suppliers
http://help.sap.com/erp2005_ehp_02/helpdata/en/93/743962546011d1a7020000e829fd11/frameset.htm
====
Credit Memo
Credit Memo
http://help.sap.com/erp2005_ehp_02/helpdata/en/a8/b99890452b11d189430000e829fbbd/frameset.htm
Creating Credit Memo / Debit Memo
http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/561076545a11d1a7020000e829fd11/frameset.htm
Creating Credit Memo / Debit Memo Requests
http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fed1545a11d1a7020000e829fd11/frameset.htm
Credit & Debit Memos
http://help.sap.com/erp2005_ehp_02/helpdata/en/a2/40418a496e11d3b3850008c719be0f/frameset.htm
Processing Credit Memo : Example
http://help.sap.com/erp2005_ehp_02/helpdata/en/4e/b3c399a1f711d194e700a0c9306794/frameset.htm
===
Debit Memo : http://help.sap.com/erp2005_ehp_02/helpdata/en/8d/a4b3880bc4c441905801d5025a5600/frameset.htm
====
Return process
You need to receipt the rejected goods through SD Module (VA01 - Sales Order type RE).
The steps are as follows :
1. Create a return request. (Using Sales Order in SD)
2. Create outbound delivery according to return request.
3. If the setting is correct in the outbound delivery screen SAP will automatically switch post goods issue button into post goods receipt. The setting is in sales order item category and delivery type.
4. In the standard system the movement type used is 651.
5. After post goods issues receipt is done using outbound delivery, the quantity is placed in blocked stock without value updating.
6. You will then decide if the return quantity are indeed bad stock or not.
7. Transfer Posting from block stock to unrestricted stock (mvt type 453), this will have accounting effect (Debit Inventory, Credit COGS)
8. Goods Issue to scrap account how to create new titles which can be used in creating the "address" view on the Vendor master.{T-Code: XK01}
In config go to Basis Components --> basis services --> Address Management --> Maintain title texts
Order type (RE)
Returns (RE) (VA01) Order will be placed as a return type order
 PGR (VL02N) post goods receipt
 Billing (VF01) --> Credit Memo is Raised
Accounting (VF02) --> Credit memo is passed to Accounting tables
===
Calcelling Invoice.
VF11 --> PGI (VL09N)
===
====
Reward if USeful
Thanx & regrads.
Naren..

I need vbeln(sales document no),vbeln1 (subsequent sd doc) in alv report.

Similar Messages

Maybe you are looking for