Related to order creation

Hi,
Could you please give some idea about new order creation as per below scenario
1) i need to create a new order for example "A" using ATG OOTB orderHolder class.
2) if the order is already exists then no need to create and but i need to iterate this order("A") from shopping cart
2) Then i need to copy commerceItem from current for example "B" order to newly created order ("A") and vice versa.
Thanks in advance.
pveedu

is it for anonymous users or logged in users?
when a req flows through DAF pipeline it creates 2 session object - Profile and Cart.
cart.getCurrent will give u the current order.
if the user is logged in u can call cart.getSaved to see if an order is already there for the user. U can set the saved order to current order.
u can merge the commerce items calling mergeOrdersCopyCommerceItem method of CommerceItemManager.
u can get reference for CommerceItemManager from OrderManager.
CommerceItemManager.mergeOrdersCopyCommerceItem()

Similar Messages

IDOC related to Order creation

Hi ,
I have to upload Sales Orders through IDOC's which I am successfully doing using ORDERS05. I am facing one issue on this, here the flat file will also have Quotation Number of which Orders have to be referred. This too has been achieved. But the issue is when I do so the SHIP TO address is being copied from the Quotation, whereas I am populating the SHIP TO in header segment of Partners which has to copied to Items.
As I said, I have maintained separate segment for Header SHIP TO but this is not copied to Items Partners, generally what ever is maintained in Header shall be copied but since I am referring to Quotation the SHIP TO is copied. How to handle this.
Bwaj.

Hi,
You create your order with reference to quotation, therefore copy routines between the documents are also activated.
I suggest to check on the copy control setup between quotation and order (VTAA transaction) especially at item level (for your item categories). Check what routine is assigned to partner copy.
Regards,
Dominik Modrzejewski

GETTING ERROR RELATED TO TASK LIST IN ORDER CREATION USING BAPI_ALM_ORDER_M

hi all ,
I am using bapi_alm_order_maintain to create a new work order . i am passing task list group and task list counter in IT_TASK_list tables . on execution it is showing an error message " PLEASE PROVIDE THE MANDATORY TASK LIST DURING WORK ORDER CREATION.
SEEKING YOUR HELP TO REMOVE THIS ERROR.

hi all ,
I am using bapi_alm_order_maintain to create a new work order . i am passing task list group and task list counter in IT_TASK_list tables . on execution it is showing an error message " PLEASE PROVIDE THE MANDATORY TASK LIST DURING WORK ORDER CREATION.
SEEKING YOUR HELP TO REMOVE THIS ERROR.

Query relating to the creation of Managed Service Accounts

Hi Folks
I am studying for my 70-411 exam and have a query relating to the creation of Managed Service Accounts.
I have successfully created an MSA account named 'MSATest' on a DC using:
new-adserviceaccount -name msatest –dnshostname home-dc-01 -passthru
and
add-AdcomputerServiceAccount -identity home-ap-01 -serviceaccount msatest -passthru
However the guide that I am using now says that I now need to run: Install-ADServiceAccount on the host computer in the domain to install the MSA in order to make available it available for use by services.
So on my member server (home-ap-01) I have installed the Active Directory Module for powershell and ran:
PS C:\Users\administrator.PCECORP> Install-ADServiceAccount -Identity msatest
Install-ADServiceAccount : Cannot install service account. Error Message: 'An
unspecified error has occurred'.
At line:1 char:1
+ Install-ADServiceAccount -Identity msatest
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (msatest:String) [Install-ADServiceA
   ccount], ADException
    + FullyQualifiedErrorId : InstallADServiceAccount:PerformOperation:Install
   ServiceAcccountFailure,Microsoft.ActiveDirectory.Management.Commands.Insta
llADServiceAccount
PS C:\Users\administrator.PCECORP>
However this errors, Have I misunderstood the purpose of the Install-ADServiceAccount ? or am I doing something wrong?
Thanks in advance for you help.

Try using -RestrictToSingleComputer parameter when creating service account with New-ADServiceAccount.
Gleb.
Hi Gleb
Thank you for your help, it is appreciated. That did the trick.
All the best.

Automatic Reservation at the time of process order creation

Hi Experts,
As you are aware, when we create a process order and save, system automatically generates the reservation and the reservation will be for movement type 261. My requirement is like this. When system creates reservation, system should consider for which order type the process order is created and create a reservation for other movement type also.
For eg. Iam having order type ZRRW. When system creates reservation at the time of order creation, system should check the order type and reservation should be created for a movement type Z11 instead of 261 in the normal case.
Is there any user exit for the same. Please let me know.
Else how can I post the goods issue with a movement type other than 261. MIGO is not accepting other movement types.
Anticipating your reply
Regards
Prathib

Hi Ayethebing,
Thanks for the reply. we created the new movement types inorder to use the SAP standard reports and get the different types of goods movements based on the different processes.
We can do the goods issue using the custom movement type through MB1A. But I was trying to use in MIGO and this is where system wont allow this.
In MIGO, system will do the goods issue based on reservation only. The reservation is created at the time of order creation and it uses movement type 261 irrespective of the order type.
I was trying to find out whether any option is there to use custom movement type to create reservation so that system would propose this movement type in MIGO for goods issue against process order.
This is an interesting case but unfortunately dont have any option of user exit or Badi. Only one user exit related to reservation is to change the str loc and back flush indicator.
@Sabine: Thanks for your reply. But the BADI that you provided wont serve the purpose.
Thanks
Prathib

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

Automatic Sales Order Creation from PO in B1

Hi,
I have this scenario. Purchase order is created in SAP B1 (Business One) which triggers automatic Sales Order creation in SAP ECC 6.0.
The requirement:
For the combination of PO number and Sold to party there should be only one sales order created.
The problem:
Sometimes for the same PO duplicate Sales orders(sometimes 3,4) are getting created in ECC.
Possible causes:
Probably no validations in the interface.
Question:
1. First of all, is it an SD issue or PI (process integration) issue.
2. If it is an SD issue, as a functional consultant what / where can we do to prevent this.
Thanks.
Edited by: SAP SD_Newbie on Oct 20, 2011 6:59 PM
Edited by: SAP SD_Newbie on Oct 20, 2011 6:59 PM
How do I move this to "ERP - Sales and Distribution (SD) General", because this question is not just related to "ERP SD Sales" but SD in general. Isn't there an option for the users to a question from one forum to another.

1. First of all, is it an SD issue or PI (process integration) issue.
- May be PI, or SD or both. I am not sure about the integration mechanism/program so I am not able to pinpoint.
2. If it is an SD issue, as a functional consultant what / where can we do to prevent this.
In t.code VOV8, go to the sales document type. Select value A in the field, check Purchase order Number. Then go to t.code OVAH, there make the message number V4 115 as error message. This will not allow the creation of the sales order, if the Purchase order number duplicates. I assume in your process, the purchase order number is populated in the PO number field of the sales order overview screen.
Regards,

Automatic creation InternalOrder inECC after Service Order creation in CRM

Hi,
After Service Order creation in CRM, the automatic creation of Internal Order in ECC not happening, needs to be do the related settings. Can anybody share the stepts for the same to do the settings.
rgds,
balu

Hello balu,
Have you released all items?
Also,please make sure that against the item category "Assign BW/CO" is set to Service.
Hope this helps!
Thanks and Best Regards,
Shanthala Kudva.

Sales order creation - data stored in which tables for customer

Hi experts,
During sales order creation, data entered during sales process is stored in various related tables. Can anyone list the tables where data is stored for customers?
Thank you

Dear Manisha
Once you saved the sale order,
- all header datas are stored in VBAK
- all item level datas are stored in VBAP
- schedule line confirmation in VBEP
- all condition types and values are stored in KONV / KONP
- Partner functions in VBPA
- Delivery related fields like Shipping Point, Delivery Date, Goods Issue etc., are all in VEPVG
thanks
G. Lakshmipathi

Error Handling for Background/Update Tasks (Transfer Order creation) - How?

Hi,
I have a standard process for creating a Transfer Order and 2 user-exits that I have implemented.
The user exits are used to transfer information during Transfer Order creation.
However, the user-exits also check data in table TVARV and other. As such, error handling needs to be implemented, since the T.O. might or might not go through, depending on data validation and related.
However, the user-exits are implemented during creation, which is an update task that runs in the background. This makes it impossible to output any information or error messages.
What else can be done in regards to outputting a message, since the user will need to see some sort of message that the process failed, that the T.O. didnu2019t confirm? Can an SAP inbox message be created and how?
Please help.
Thank You,
John

Hi,
Please check the following link for all the function modules and user exits on TOs.
http://help.sap.com/saphelp_erp2005/helpdata/EN/c6/f83a294afa11d182b90000e829fbfe/content.htm
Reward points if it was helpful.
Regards
Abhishek
Edited by: Abhishek Raj on May 29, 2008 10:20 AM

Condition types in Sales order creation process

Hi Friends...
While creating the sales order with BAPI,
What is the condition type i have to pass for pricing procedure...
There many condition types for my pricing procedure, which one o have to select...
Some of them are mannual, and other reuired, which one I have to pass?
I want the information related to this condition types.., as here no SD consultant availble for me.
Sales order creation, Line item error
Thanks,
Naveen.I

Hi Friends...
Please let me know is it mandatory to give condtion type while creating the sales order...?
I am using BAPI_SALESORDER_CREATEFROMDAT2 to create my sales order...
http://www.sap-img.com/abap/bapi-salesorder-createfromdat2.htm
Thanks,
Naveen.I

User-Exits stop working in automated purchase order creation

Dear all,
we used to create sales orders with transaction VA01 and then separately call ME21N to create a purchase order.
In saving the purchase order we activated user-exit EXIT_SAPMM06E_012 to process some extra logic we need here.
Now we changed to process for SAP to automatically create the purchase order (to eventually be able to automate the entire process, including sales order creation). Ever since we did that, the user exit is not called any more!
Does anyone know why? If I manually open ME22N and save the PO, it works! We have to find a way to run the logic in the user-exit during automated PO creation just for the volume of orders.
Besides that, we're still looking for a convenient way to update PO confirmations using a BAPI or other function module.
Thanks for your help!
regards,
Johannes.

Good question
User-exit may not work as the function modules [ and not ME21N ] called in the Sales Order --> Purchase Req --> Purchase Order process may not call the enjoy user-exits.
Further, this process of automated PO works on Business Obejct event trigger.
So a event is triggered [ ALECREATED ] on Sales Order Business at the time of Sales Order Creation.
This event is linked with a function module called PUR_ORDER_CREATE_VIA_SD_EVENT.
similarly for change it is PUR_ORDER_CHANGE_VIA_SD_EVENT.
If you go through the FM code, you can make out how to utilize this FM as user-exit.
However you need to make the change in this FM after copying the related function group to a Z one. And then change the event linkage accordinlgy to call the new FM.
See Business Workflow --> Events section..
If you are not sure about how to do the event linkage then ask it in BPM section...[ They will request you to get lost ...no no ..they didn't do it to me ..just kidding ]
Cheers,
Ram

MDVEX table in order creation (VA01)

Hi,
Can anybody let me know , where does the table "mdvex" gets populated from during order creation (VA01) ?
I tried debugging , but cudn't figure out.
Thanks!
-Faria

Hi Faria,
Delivery date is calculated by scheduling. FM sd_scheduling is the one that calculated delivery date LFDAT. Requested Delivery date is set to this FM then based on .The system calculates the material availability date by working backwards from the customer's requested delivery date, taking into account how much time is needed for delivery-related procedures, such as picking, packing, loading, and transportation. All these times are defined in the routes and factory calendar. Per the settings you have in the customising , a new delivery date is set. After this FM, FM availability_check_controller is called. If the stock is available on the delivery date MDVEX will be filled.If the stock is confirmed on late date then scheduling is called again and new delivery date is set based on the parameters.
Hope this information helps
Thanks
Amber

Sales order creation -pricing- IDOC processing

Hi All,
Issue is related to pricing procedure and condition types while processing the IDOC for sales order creation.
The condition type ZSTD maintained in the pricing procedure AAAA, has reference condition type as ZZZZ, when we are processing IDOC, system is throwing error as " condition type ZZZZ, is not maintained for A V AAAA.
This error will not populate when we create the sales order manually.
Kindly let me know if programs needs to be checked and or any configuration mistakes involved in this.
Regards,
SAN

>
Vivek Baddula wrote:
> Hey Teju,
>
> Could you pls put me the block of code how you are populating to the idoc edidd. So that we can guide you.
>
> And also tell me the message status 51 in IDoc what it is showing , and also see the segment( maybe E2EDP05) specific to pricing for the IDoc you populated.
>
> Regards,
>
> Vvieks
>
> 'Grow and help others to Grow'
Vivek,
Thanks for the reply.
Status 51 reads "condition ZPRL is missing in pricing procedure A V ZPRINT, WE are not passing any value as a part of tsting. The system should pick price values from condtion record.

Problem submitting batch request for sales order creation

Hello experts,
I have created a gateway service, implementing the CREATE_DEEP_ENTITY for order creation. I have tested my service with the Chrome Advanced Rest Client and it works fine with the following XML request:
<?xml version="1.0" encoding="UTF-8"?>
<atom:entry xmlns:atom="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<atom:content type="application/xml">
<m:properties>
<d:OrderId>0</d:OrderId>
<d:DocumentType>TA</d:DocumentType>
<d:CustomerId>C6603</d:CustomerId>
<d:SalesOrg>S010</d:SalesOrg>
<d:DistChannel>01</d:DistChannel>
<d:Division>01</d:Division>
<d:DocumentDate m:null="true" />
<d:OrderValue m:null="true" />
<d:Currency m:null="true" />
</m:properties>
</atom:content>
<atom:link rel="http://schemas.microsoft.com/ado/2007/08/dataservices/related/SOItems" type="application/atom+xml;type=feed" title="SALESORDERTSCH.SOHeader_SOItems">
<m:inline>
<atom:feed>
<atom:entry>
<atom:content type="application/xml">
<m:properties>
<d:OrderId>0</d:OrderId>
<d:Item>000010</d:Item>
<d:Material>C20013</d:Material>
<d:Plant m:null="true" />
<d:Quantity m:Type="Edm.Decimal">100.000</d:Quantity>
<d:Description m:null="true" />
<d:UoM m:null="true" />
<d:Value m:null="true" />
</m:properties>
</atom:content>
</atom:entry>
<atom:entry>
<atom:content type="application/xml">
<m:properties>
<d:OrderId>0</d:OrderId>
<d:Item>000020</d:Item>
<d:Material>C20014</d:Material>
<d:Plant m:null="true" />
<d:Quantity m:Type="Edm.Decimal">200.000</d:Quantity>
<d:Description m:null="true" />
<d:UoM m:null="true" />
<d:Value m:null="true" />
</m:properties>
</atom:content>
</atom:entry>
</atom:feed>
</m:inline>
</atom:link>
</atom:entry>
Now that my service is working, I want to be able to call it from a SAP UI5/Javascript application. In order to process multiple items for one order header, I use the OData batch request. Here is my Javascript method that is being processed:
executeOrderCreation : function() {
// Retrieve model from controller
var oModel = sap.ui.getCore().getModel();
oModel.setHeaders(
{ "Access-Control-Allow-Origin" : "*",
"Content-Type": "application/x-www-form-urlencoded",
"X-CSRF-Token":"Fetch" }
// Define data to be created
var headerData = {
OrderId : "0",
DocumentType: "TA",
CustomerId : "C6603",
SalesOrg : "S010",
DistChannel : "01",
Division : "01",
DocumentDate : null,
OrderValue : null,
Currency : null,
varItemData1 = {
OrderId : "0",
Item : "000010",
Material : "C20013",
Plant : null,
Quantity : "100.000",
Description :null,
UoM :null,
Value :null,
varItemData2 = {
OrderId : "0",
Item : "000020",
Material : "C20014",
Plant : null,
Quantity : "100.000",
Description :null,
UoM :null,
Value :null,
var batchChanges = [];
oModel.refreshSecurityToken(function(oData, oResponse){
alert("Refresh token OK");
}, function() {
alert("Refresh token failed");
}, false);
oModel.read('/SOHeaders/?$Batch', null, null, false, function(oData, oResponse) {
// Create batch data
batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",headerData ));
batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",varItemData1 ));
batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",varItemData2 ));
oModel.addBatchChangeOperations(batchChanges);
// Submit changes and refresh the model
oModel.submitBatch(
function(oData) {
oModel.refresh();
function(oError) {
var error = oError;
alert("Read failed" + error);
false);
}, function() {
alert("Read failed");
The result is when I submit the batch, I have an error saying: The following problem occurred: no handler for data -
Am I doing right in the batchChanges creation ? (Header then items)
Why am I facing this error ?
Any help would be greatly appreciated.
Thanks and regards,
Thibault

Hi,
you should also have '/' before collection name so that it will be /SOHeader and as below.
batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",headerData )); batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",varItemData1 ));
batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",varItemData2 ))
Regards,
Chandra

Related to order creation

Similar Messages

Maybe you are looking for