Territory information for sales Order

Hello,
We are trying to find territory/sales person information for an Order. When we entered the order then we do not enter sales person name, so now we are trying to find territory/sales person information
Based on Territory setup, like sales order customer name or zip code etc…is there any public api which can be used to find this information. We are doing kind of reverse engineering…like find the sales rep information for an order …
Thanks
Deepak

793318 wrote:
Hello,
We are trying to find territory/sales person information for an Order. When we entered the order then we do not enter sales person name, so now we are trying to find territory/sales person information
Based on Territory setup, like sales order customer name or zip code etc…is there any public api which can be used to find this information. We are doing kind of reverse engineering…like find the sales rep information for an order …
Thanks
DeepakI'm not sure about the api's but here is how you can get through it..
Since you've the order information, you know who the customer is. Get the party information of the customer from hz_parties.
Now, it is going to be little tricky to find out the right sales rep based on how the territories and how the upstream processes is handled - let us go one by one -
I'm assuming this is some kind of conversion activity and you are trying to find out who the sales rep was?
Alright, If this order was generated from a quote you always have a reference. If it does not have a quote, does it tie back to an opportunity/lead? if yes, use the party information identified in the earlier step - identify how many opportunities are there? if it is more than, see if the right product is captured on the opportunity...if No, then it is tricky and you have to by creation date or atleast by last_updated_date. And, the owner on the opportunity or lead would be your sales rep.
Now, if you dont have an opportunity/lead....how am I going to find out.......
Again, you hve the party information, check who is on the sales team. if there is more than one sales rep, you have to see where these sales reps fall into and in which territory........
In simple words - if you have more than one sales rep who can work on a given lead or opportunity and if you dont have any other custom attributes identified at the territory level, it would be tough to identify the right sales rep....
hey, by the way - if you have commissions and if you have paid the commissions, you can find out the right sales rep......that is down stream!!!!
HTH

Similar Messages

Fetch Tax Information for Sales Order

I have a sales order where I pass the variable IS_BIL_INVOICE to my smartform. There I grabbed all the tax information from the table IS_BIL_INVOICE-HD_KOND. For some reason this header table is no longer being populated with the tax information.
I am wondering two things:
1) Why is this not being populated anymore when I create a new sales order and how do I fix it?
OR
2) In what tables can I pull out this information using information that is attainable to me (sales order #, sales item #, etc.)? I need to pull out tax code, tax rate, and tax amount for each tax code applicable to the item.

Hi,
Check if the pricing procedure has been changed in V/08..
For the corresponding condition types in the the pricing procedure it should have print columns populated with 'S' (I guess for header conditions)...Please check with your SD functional consultant for more details.
Thanks
naren

Outbound IDOC BW to R/3 for sales order information

Hello everybody,
is there someone, who has any experience with transferring data (sales order data) <b>from BW to R/3</b> via IDOC.
The customer has already implemented an EDI interface for R/3 via IDOC for generating sales orders. This IDOC interface should be used also for transferring BW data to R/3. So BAPI and flatfile interface BW-R/3 is not favored!
Is there any good documentation how to proceed which can be provided to me?
In particular i am interested how to create a function module to fill an IDOC structure from a standard data base table in BW (ODS table), how to create new message types etc.
Thanks in advance
Gunnar

Is it possible in general?
Yes, theoretically at least.
You do not have SAP standard IDOCs (ORDERS*) for Sales Orders, neither is the functions or message types etc available on BW system. This would mean you will have to create custom idocs/message-type/process-code and configuration setup. In addition, if you are going to read data from a cube (to create the orders), it is going to be a slow and painful work.
Another option, if you do have to create sales order IDOCs, would be to extract order data from BW to a , say Infospoke file, on BW. You can process this file in R/3 system to create/post a sales order idoc. This would help as the necessary components (eg sales order IDOC) are available there already. If you need help on that (creating sales order IDOC or BAPI posting, from a file), ABAP forum would be more helpful.

Query for Sales Order Analysis

Dear Experts
I have written a Query for Sales Order Analysis and would like to have help on this.
The query is used for generating daily report for Sales Order on number of documents (Sales Order), total amount of sales orders and total GP of Sales Order. The query is written as below:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum] ORDER BY T0.[DocNum]
where U_Total_GP is a UDF for storing the GP of each order.
After executing the query, a selection criteria of date appears and after a date is selected, the report shown information required. However, the query does not calculate column total for total amount and total GP. Although I know the total for each column can be displayed by pressing "Ctrl" + Click on the column title, it would have to be done from time to time.
Therefore, I would like to modify my query in order to calculate the column totals when executed. Are there any suggestions for this?
Thank you
Regards
Elton

Hi Elton,
Try this:
SELECT T0.[DocNum], SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0] GROUP BY T0.[DocNum]
Union ALL
SELECT '', SUM(T0.DocTotal) AS 'Total', SUM(T0.U_Total_GP) AS 'Total GP'
FROM ORDR T0 WHERE T0.[DocDate] =[%0]
ORDER BY T0.[DocNum]
Thanks,
Gordon

How to see archive data for Sales order

Hi all,
I am working on PS , network is created with sales order 10911. the components are added while sales order created, but after that someone deletes the sales order, because now it is showing oder does not found, where i get the entreis for sales order.
Regards,
Khushi.

Hi Khushi,
To see the archived data for sales order , go to transaction code SARA.
Choose object name as SD_VBAK.Click READ.
It will show a screen giving a name of program and option to execute in background or foreground.
It will help you to get information about archived sales order data.
Hope it helps you.
Thanks,
Sarita singh Rathour
Edited by: Sarita Rathour on Aug 28, 2009 7:46 AM

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Delivery information of sales order in CRM

hi,
I am creating a sales order in CRM. Suppose there are 3 line items in this order.
Where do i find all delivery related information for this order in crm system? or i have to go to ECC system to get this info?
Thanks,
Shantanu

thank you shrikant.
we are using trading contract , so we dont need delivery information from ECC anymore.
Thanks.

Interactive report for sales order

how to create an Interactive Report which displays all the sales orders for one particular customer, the materials ordered, quantity ordered, goods issue date of that particular order and contact information about that particular customer.

http://www.sap-img.com/abap/program-for-sales-order-by-customer-date-sales.htm
https://forums.sdn.sap.com/click.jspa?searchID=2651341&messageID=1671145.
Have a look at the demo programs,
DEMO_LIST_INTERACTIVE_1
DEMO_LIST_INTERACTIVE_2
DEMO_LIST_INTERACTIVE_3
DEMO_LIST_INTERACTIVE_4
DEMO_LIST_HIDE
Please give me reward points.
Regards,
Murali Poli

How to configure rescheduling for sale order quantities

kindly explain how to configure rescheduling for sale order quantities that are created last month. kindly explain. i am in urgent.
regards,
g.v.shivakkumar

Hi,
Short text
Rescheduling sales and stock transfer documents: by material
Description
The 'Rescheduling' program (SDV03V02) processes sales document items that are contained in the item directory for the material. It takes into consideration open items and schedule lines from stock transfer items, stock transfer scheduling agreements and purchase order requests (items only), referred to hereafter as stock transfer documents, for the materials.
All sales documents for the material that are still open are selected. This means that the material index must be activated for at least all sales document types, whose items may have requirements. All stock transfer documents or items for the material that are still open are also selected. Open in this case means for example, that there is no deletion indicator, that the item from a stock transfer purchase order request cannot be labeled as completed or that the quantity delivered and posted to goods issue for the item in a stock transfer purchase order is the same as the amount ordered. An availability check can only be carried out if a checking rule is assigned to the document type - if this is not the case, the document or document item is not checked.
Checking rule 'A' is used as a basis for rescheduling sales orders (exceptions to this are rush orders they use checking rule B, and orders with individual customer stock; they use checking rule AE). Stock transfer documents use the checking rule that is assigned in Customizing for Purchasing. It is important that the scope of checks is consistent for both the stock transfer documents and the sales documents and that they do not exclude each other, as this can lead to incorrect test results. An example of an incorrect setting would be: The scope of check for checking rule 'A' checks delivery schedules for stock transfer purchase orders and stock transfer purchase requests, however the scope of check for the checking rule for the stock transport scheduling agreement does not.
The items and schedule lines found in the selection are sorted according to 'Priorities' - document category, delivery priority, creation date of the item or schedule line (for stock transfer purchase orders and delivery plans) entered on the selection screen or according to the schedule line date of the earliest schedule line with order quantity, document number and item number and then transferred to the availability check. Priority 1 is highest priority and priority 5 the lowest. Stock transfer purchase order requests are sorted after stock transfer purchase orders and scheduling agreements, as they are less binding. This means that when you have identical sort criteria such as delivery dates, the stock transfer purchase order item is checked first and then the item from the stock transfer purchase order request.
The preset option 'Unconfirmed documents required' only carries out rescheduling for materials for which there is at least one unconfirmed transaction.
You can use the parameters 'Sorting criteria delivery date' to define whether sorting is carried out with the order quantity after the creation date of the item or the delivery date of the earliest schedule line.
If you mark the 'Simulation' field, the checked documents are not saved. Instead a results list is generated and saved. However, the availability check for the corresponding documents continues as if saving has taken place already, that is, that the simulated list corresponds to the actual one.
Under 'Options' on the selection screen, specify whether sales documents and/or stock transfer documents should be processed. For stock transfer documents you can enter whether stock transfer purchase orders and scheduling agreements should be processed at item or schedule line level:
Processing at item level:
All open schedule lines for the item are read and collected, then transferred to the availability check. To sort and prioritize documents, you do not need each individual schedule line. It is sufficient to have the item or data from the first schedule line. All open schedule lines for the item are processed and checked.
Example of processing at item level:
Sorting: Date (Delivery date first schedule line) - Document number - Document item
Doc. cat. Doc. number Doc. item Doc. schedule line Delivery date PO        4500000012      10               0001              26.01. PO        4500000012      10               0002              26.02. PO        4500000025      20               0001              28.01. PO        4500000025      20               0002              02.02.
You can see that the second schedule line for document 4500000025/20 from 02.02 was processed after the second schedule line for document 4500000012/10 from 26.02. This is because all open schedule lines for an item are read and processed. The first schedule line from 4500000012/10 has the earliest delivery date, therefore it has priority.
Processing at schedule line level:
Each open schedule line for an item is entered in document sorting in accordance with the values entered under 'Priorities'. The availability check is carried out for each individual schedule line.
Example for processing at schedule line level:
Sorting: Date (delivery date first schedule line) - document number -document item
Doc. cat.    Doc. number Doc. item Doc. sched. line Del. date PO           4500000012    10             0001           26.01. PO           4500000025    20             0001           28.01. PO           4500000025    20             0002           02.02. PO           4500000012    10             0002           26.02.
Here you can see that each schedule line was sorted according to its delivery date. Note that this type of processing requires more runtime due to the individual checks and more frequent saving.
The results of rescheduling are saved, as long as the program was not started in simulation mode. When calling up from the 'Sales' area menu or when directly starting via the development environment, the iniator is informed via a dialog box that he has just started a process that changes data. He can then decide whether or not he wants to continue.
Checking procedure for stock transfer documents:
An availability check of stock transfer documents in rescheduling is carried out in accordance with the check carried out when manually creating a document. If, however, the required quantity for a schedule line is not available on a particular date and will not be ready until later, new schedule lines are created for the stock transfer purchase orders and scheduling agreements, containing the relevant data. New items are created in this case for stock transfer purchase order requirements. The total sum of schedule line quantities for a processed schedule line corresponds to the schedule line quantity of the original schedule line.
First example: Using a stock transfer purchase order item with a schedule line:
a) Status of item before rescheduling run:
Del. date PO quantity   Confirmed quant Confirmed del. date 23.07.      50 items       0 items              -
==> This now affects the stock/requirement situation:
    - Goods issue is posted for the material in the delivering plant on the 23.07.
    - A purchase order of 10 items was created for the material in the delivering plant. Delivery is expected on the 29.07.
b) Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity   Confirmed quant   Confirmed del. date 23.07.     40 items      40 items            23.07. 29.07.     10 items      10 items            29.07.
==> The first schedule line was changed in accordance with the results of the rescheduling availability check. Only 40 of the 50 original items could be delivered on the 23.07. Therefore, a new schedule line is created for the rest on the 29.07. for 10 confirmed items.
Second example: Same output situation as the above example.
==> There is now a change in the requirement/stock situation:
A purchase order for 10 items is created for the material in the delivering plant. Delivery is expected on the 29.07. A further purchase shows another 40 planned items on the 30.07.
   Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 29.07.     10 items       10 items          29.07. 30.07.     40 items       40 items          30.07.
==> The first schedule line was changed in accordance with the result of the availability check for rescheduling. The original delivery date is set to the date confirmed in the ATP check. A new schedule line is created for the remaining 40 items, that are available on the 30.07.
Note:
Any set fixed delivery date and quantity indicators and creation indicators for schedule lines or items are 'inherited' by newly created schedule lines. Assuming that the original schedule line was fixed in the above example (since it is created manually), this indicator is also set for the newly created schedule line.
If shipping scheduling is activated for a stock transfer document type, this is also implemented for newly created schedule lines, with the exception of route schedule determination. This means that in the current version of the program no route schedule has been determined for a schedule line containing a route schedule for which new schedule lines may need to be created.
The results of the run are issued in the form of a list, which is also saved, so that the results can be controlled at a later date. This is done using the function 'Evaluate rescheduling', but it is only a good idea to do this after the first rescheduling has taken place. You can restrict selection requirements but these can however affect the runtime. You can use this function to analyze the saved list until the next rescheduling run, which writes over the result. If you start rescheduling in the background, a spool file with the result list referred to will be created in the corresponding setting. You can see this in spool management.
Output
A list of changed documents, a list of documents in which an error occurred during processing and as a result were not changed, can be called up via the menu 'Edit - Error log'. If in a subsequent evaluation a restricted selection is carried out, a note appears at the end of the list to say that not all document items are displayed.
You can set the scope of the list under the menu option 'List' in the list display. You can view improvements, deteriorations and the whole list. Before the documents can be included in one or either of the restricted lists, the date or quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents.
You can use the interface for changing transactions and the order list to navigate. Use 'Back' to exit the list and 'New selection' to return to the selection screen.
Recommendation
You should only start this program occasionally and use very restricted selectin criteria during working hours as it requires enormous system resources.
Note
The columns for 'New date' and 'New confirmed qty' only contain entries if the dates or quantities have changed.
As the system only runs the change check (dates/quantities) per line in the original list, an item whose backlog has increased in the list of improvements. This occurs, for example, if the whole quantity can be delivered at once but at a later date. In this situation, the system determines an increase for the line when it compares quantities.
Regards,
Amrish Purohit

Table name for sales order with Customer info

Hi Gurus,
Could you please provide me table name for sales order with customer no and customer name.
I have list of sales order number (more than 1000 no's ) i need to identify customer number and customer name (ship to party and sold to party information). I am running this report every week. so i plan to create sqvi for this report.
Thanks and regards,
B.Deethya.

Hello,
Access Tables VBAK & VBAP.
From the above tables you will get Solt to Party & Ship to Party Codes.
For Customer names you have to pass the Customer Codes to Table - KNA1
Hope this clarifies.
Thanks,
Jignesh Mehta

Entering payment cards information in sales order

Hi Folks,
I am uploading the payment cards information in sales order using transaction VA02. I need to check if there is an already existing payment card in order to know the line number to enter the new card information. I know that FPLTC table has the information about the payment cards. How can I read the already existing lines and pass the new card information in the new line?
Thanks,
RAJ

Tables: VBAK, FPLTC, FPLA.
Hi,
I am attaching my code. It would be really helpful for me if someone can tell me what should be the exact key to read the data. Somehow only one condition is true in this case.
Data : Begin of itab occurs 0,
       VBELN(10) type C, "Sales order Number
       AUTWR(15) type C, "Maximum amount
       end of itab.
DATA : Begin of itab1 occurs 0,
       FPLNR LIKE FPLTC-FPLNR,
       FPLTR LIKE FPLTC-FPLTR,
       ccnum like FPLTC-CCNUM,
       CCINS LIKE FPLTC-CCINS,
       END OF ITAB1.
DATA : ITABH LIKE ITAB OCCURS 0 WITH HEADER LINE,
       ITABI LIKE ITAB OCCURS 0 WITH HEADER LINE.
include bdcrecx1.
Parameter : PATH(128) OBLIGATORY.
start-of-selection.
CALL FUNCTION 'WS_UPLOAD'
    EXPORTING
      FILENAME = PATH
      FILETYPE = 'DAT'
    TABLES
      DATA_TAB = itab.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SORT ITAB1.
Select FPLTCFPLNR FPLTCFPLTR FPLTCCCNUM FPLTCCCINS into
corresponding fields of itab1 from FPLTC INNER JOIN vbak on fpltc~Fplnr
eq vbak~Rplnr.
   ENDSELECT.
ITABH[] = ITAB[].
ITABI[] = ITAB[].
SORT ITABH.
DELETE ADJACENT DUPLICATES FROM ITABH COMPARING vbeln.
perform open_group.
Loop at itabh.
    perform bdc_dynpro       using 'SAPMV45A' '0102'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'VBAK-VBELN'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '/00'.
    perform bdc_field        using 'VBAK-VBELN'
                                    ITABh-VBELN.
    perform bdc_dynpro       using 'SAPMV45A' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '=KRPL'.
Read table itab1 with key FPLNR = VBAK-RPLNR.
    perform bdc_dynpro       using 'SAPLV60F' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '/00'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'RV60F-CCBEG(03)'.
    perform bdc_field        using 'FPLTC-CCINS(03)'
                                    'CHCK'.
    perform bdc_field        using 'FPLTC-CCNUM(03)'
                                    '0000000000000001'.
    perform bdc_field        using 'CCDATE-EXDATBI(03)'
                                    '12/2009'.
    perform bdc_field        using 'RV60F-CCBEG(03)'
                                    'X'.
if sy-subrc <> 0.
    perform bdc_dynpro       using 'SAPLV60F' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '/00'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'RV60F-FAKWR(02)'.
    perform bdc_field        using 'RV60F-FAKWR(02)'
                                   ITABh-AUTWR.
    perform bdc_dynpro       using 'SAPLV60F' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '=CCMA'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'FPLTC-CCINS(02)'.
    perform bdc_field        using 'FPLTD-SELKZ(02)'
                                    'X'.
else.
    perform bdc_dynpro       using 'SAPLV60F' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '/00'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'RV60F-FAKWR(01)'.
    perform bdc_field        using 'RV60F-FAKWR(01)'
                                   ITABh-AUTWR.
    perform bdc_dynpro       using 'SAPLV60F' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '=CCMA'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'FPLTC-CCINS(01)'.
    perform bdc_field        using 'FPLTD-SELKZ(01)'
                                    'X'.
endif.
    perform bdc_dynpro       using 'SAPLV60F' '0200'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'FPLTC-AUTWR'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '/00'.
    perform bdc_field        using 'FPLTC-AUNUM'
                                    '111'.
    perform bdc_field        using 'FPLTC-AUTWR'
                                    ITABh-AUTWR.
    perform bdc_dynpro       using 'SAPLV60F' '0200'.
    perform bdc_field        using 'BDC_CURSOR'
                                    'FPLTC-AUNUM'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '=BACK'.
    perform bdc_dynpro       using 'SAPLV60F' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '=S\BACK'.
   perform bdc_field        using 'BDC_CURSOR'
                                   'FPLTC-CCINS(05)'.
    perform bdc_dynpro       using 'SAPMV45A' '4001'.
    perform bdc_field        using 'BDC_OKCODE'
                                    '=SICH'.
    perform BDC_TRANSACTION using 'VA02'.
ENDLOOP.
perform close_group.

BAPI for Sales Orders items

I'm looking for BAPI, which returns all items for sales order.
Returned items must have included all information, which we can see in transaction va02 on card Item Overview
I'll reward with points for good BAPI.
BR Tomek

In the i_bapi_view structure, populate which tables you would like to have returned by using a value of X.
Use the sales documents table to pass which documents you want information on.
So if you wanted item details:
i_bapi_view-item       = 'X'.
sales_documents-vbeln = '0000012345'.
append sales_documents.
      call function 'BAPISDORDER_GETDETAILEDLIST'
           exporting
                i_bapi_view         = i_bapi_view
           tables
                sales_documents     = sales_documents
                order_items_out     = order_items_out.

TABLE/FIELD FOR SALES ORDER'S SHIP TO LOCATION

Hi everyone,
Does anyone tell me what is the related tables/fields for Sales Order's Ship To Location? Since I want to display the Ship To Location information in the Oracle Report in Oracle Apps R11i.
I tried to use the following SQL select statement to retrieve the Ship to address:-
-- SHIP TO LOCATION
select a.address_id, c.customer_name, C.CUSTOMER_ID, A.SITE_USE_ID from ra_Site_uses_all a, ra_addresses_all b, ra_customers c
where a.site_use_code = 'SHIP_TO' and
a.status = 'A' and
     b.address_id = a.address_id and
     c.CUSTOMER_ID = b.CUSTOMER_ID and
     b.status = 'A' and
     c.customer_id in (select customer_id from ra_customers) and
     c.status = 'A' and
     c.customer_name like 'CLARION (H.K.)%'
But I found that the data is BILL TO address. Can anyone help me? Thanks.

Hi all, I managed to solve my problem. Here's the query in case someone need it. Thanks
SELECT party.party_name "Send to" (SELECT party.party_name
FROM hz_cust_site_uses_all bill_su,
hz_cust_acct_sites_all bill_cas,
hz_party_sites bill_ps,
hz_locations bill_loc,
hz_parties party,
oe_order_headers_all h
WHERE h.invoice_to_org_id = bill_su.site_use_id
AND bill_su.cust_acct_site_id = bill_cas.cust_acct_site_id
AND bill_cas.party_site_id = bill_ps.party_site_id
AND bill_loc.location_id = bill_ps.location_id
AND bill_cas.party_site_id = bill_ps.party_site_id
AND bill_ps.party_id = party.party_id
AND h.order_number = 'your_order_number') "Invoice to"
FROM oe_order_headers_all h,
hz_cust_site_uses_all ship_su,
hz_cust_acct_sites_all ship_cas,
hz_party_sites ship_ps,
hz_locations ship_loc,
hz_parties party
WHERE h.ship_to_org_id = ship_su.site_use_id
AND ship_cas.party_site_id = ship_ps.party_site_id
AND ship_su.cust_acct_site_id = ship_cas.cust_acct_site_id
AND ship_cas.party_site_id = ship_ps.party_site_id
AND ship_ps.party_id = party.party_id
AND ship_loc.location_id = ship_ps.location_id
AND h.order_number = 'your_order_number';

Product cost collector for sales order related production

Hi Friends,
This is Azam and here i am new to this discussion forum.
we are in situation that use diffrent variant for configurable material in sales order related production,
I would like to have some information about use product cost collector for this kind of sales order related production,
also I want to know difference between prelimanary cost estimate or cost estimate for sales order?
Please co-operate me.
I would be highly appriciated if you can respond at the earliest.
Thanks
Azam

Hi,
Here, for each sales order item, you will have sales order cost estimate. This enables the system to compute the variances once the actual costs are booked against the production.
In the case of preliminery cost, we get the preliminery cost for production order as a plan cost and is not being used for the computation of variance but only for comparision purpose which is very marginally used.
Trust this helps much and do encourage our efforts!
Cheers!

Regarding bapis for sales order creation and modification

Hi,
I am trying to create a syncbo for sales order creation, modification and display. The bapis that I am using are
1.BAPI_SALESORDER_GETLIST
2.BAPISDORDER_GETDETAILEDLIST
3.BAPI_SALESORDER_CREATEFROMDATA1
4. BAPI_SALESORDER_CHANGE
Am I using the correct bapis. When I tried to create a syncbo it gave the following errors
BAPISDORDER_GETDETAILEDLIST does not have RETURN parameter in export or tables parameter
RETURN parameter in Create BAPI Wrapper should refer to structure BAPIRET2
RETURN parameter in GetList BAPI Wrapper should refer to structure BAPIRET2
GetDetail BAPI Wrapper does not have RETURN parameter in export or tables parameter
No Export parameter referring to header structure exists in GetDetail BAPI Wrapper
No Import parameter referring to header structure exists in Create BAPI Wrapper
No Import parameter referring to header structure exists in Modify BAPI Wrapper
No Import parameter referring to a field of header structure exists in GetDetail BAPI Wrapper
No Export parameter referring to a field of header structure exists in Create BAPI Wrapper
No Tables parameter referring to item structure exists in Create BAPI Wrapper
No Tables parameter referring to item structure exists in Modify BAPI Wrapper
I am informed that the above bapis are standard bapis.
I am not sure as to why I am getting the errors.
Does the syncbo require the bapi's to be in a specific format.
What would be the header and item structures for sales order bapis
Regards
Raja Sekhar

Hi Raja,
ya , for creating Sync BOs ,our BAPI wrappers must satisfy certain conditions..
just go through this link.
u can use the standard BAPIs of SALES Order in ur Custom BAPI Wrapper
http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/content/appdev/smartsync/what_is_a_bapi_wrapper.html
the RETURN must be of type BAPIRET2..
Regards
Kishor Gopinathan

Territory information for sales Order

Similar Messages

Maybe you are looking for