While we create Sales order in CRM for Madhya Pradesh State JIVP (VAT Payable) showing twice in order

Dear SAP,
While we create Sales order in CRM for Madhya Pradesh State JIVP (VAT Payable) showing twice in order, but calculation has taken one time i.e. 14%, only JIVP displaying twice (Attached Screen shot S3.JPG) in CRM order, when comes to ECC side it is showing correct entry (Attached Screen shot S4.JPG) .
Due to duplicate condition records exist in CRM table CNCCRMPRCUS956 (Attached Screen shot S1 & S2.JPG).
This happens for MP state, as duplicate entry exist with MP state only,
Please guide us to resolve the same.
Regards,
JK

Hi JK,
There is two thing. first is that when you create a sales order very same time pricing conditions added in the transaction as per the pricing procedure add for transaction type. these pricing procedures are transaction type specific not state or country specific so it will work. check here you are getting duplicate condition ?
When ever you add material in the transaction that very time one the basis of the pricing condition added in the transaction IPC method do pricing. check after adding material in transaction duplicate condition is coming ?
Secondly whenever the document replicates in ERP re-pricing again happening on conditions so theses conditions get corrected in ERP. Here if document is re-priced then system will consider it as change so again there suppose to be Bdocs get created from ERP to CRM again overwrite document so condition will be synchronized in CRM . I would request check the same too and revert.
Thanks,
Prem,

Similar Messages

  • I ordered at around 12:30AM pacific and it does not show in my order history.  When I look it up on the order status page, it just says "received and processing".  Do I have any chance of getting it on friday?

    I ordered at around 12:30AM pacific and it does not show in my order history.  When I look it up on the order status page, it just says "received and processing".  Do I have any chance of getting it on friday?

    It seems to depend on a variety of different things.
    Verizon appears to be going by the process time of orders, and not the order time of orders.  Your process time will be the timestamp on your confirmation email.
    It also depends on which model, GB, and color you ordered.  The 6+ were in high demand and low supply.
    It also depends on which warehouse (order location) your order was being processed through.  Verizon reps have told me that some warehouses have more of certain phones than others, and if your order went to a warehouse that doesn't have enough of that particular phone then you are SOL and will have to back for a backdated order.
    There is a possibility you will get it, but if you ordered any of the 6+ models, then it is unlikely.

  • Error while deploying Internet Sales B2B Web- Application for CRM 7.0

    Hi,
    I am getting the an error when I invoke the below urls. I am working on ISA application.
    http://localhost:port/xxx/b2b/init.do
    http://localhost:port/xxx/admin/xcm//init.do
    The code was build successfully without any errors.
    Error:
    Application error occurred during request processing.
    Details: Error [javax.servlet.ServletException: Initialization of Extended Configuration Management failed.
    Could not initialize XCM configuration in Database.
    Check if you have deployed the Software Component 'SAP JAVA DATA DICTIONARY 5.0'].
    Exception id: 44455354420000790000005000001D3400047AAFFB0A8DAC
    Could any one please help me in solving this?
    Regards
    MQ

    Hi,
    It seems that you have not deploy Java Dictionary Component. It is required component on machine where you want to deploy ISA. It stores your XCM related setting and value.
    First deploy SAPCRMDICxxxxxxx.SCA file then define default application scenario in your /b2b/admin/xcm/init.do. Restart your B2B application and then trr to access it.
    If you are trying to access custom ISA application you have to set application scenario for it. /b2bxxx/admin/xcm/init.do
    First deploy SAPCRMDIC component SCA file you can get it from Service market place or you can ask your SAP  Basis person.
    eCommerce Developer

  • Error while TOC created when change document  approvle for UNIT testing

    Hi All,
    During change document approval for unit testing, we are getting error, when I checked in detail, it is giving error for transport of copies error as below
    it seems to be getting locked with original transport,
    also I can't see change in transport of copies
    Does someone has any idea?
    Dinesh

    Hello Dinesh,
    Perhaps the tasks of the Transport Request were not released.
    Try to release the tasks only (from your DEV system), then choose action "Pass normal change to test". This will generate a ToC to be transported into your QAS.
    Then from the Task List, you can schedule the background job to import the ToC into QAS system.
    Regards,
    Daniel

  • Statechart Module: What is the order of execution for a parent state and its substates?

    Hello,
    This page describes the order of execution of transitions and actions for one level of nesting. What about compound states? Do the static reactions of the parent state execute before the transitions of the sub-states?

    Hello, 
    I'm not incredibly familiar with the Statechart module, but I will look into it for you on our internal database. In the mean time, there are some examples that may answer some of your questions here:
    https://decibel.ni.com/content/docs/DOC-8716
    and here:
    http://www.ni.com/white-paper/7425/en
    -N
    National Instruments
    Applications Engineer

  • Dump saving sales order in CRM

    Hi experts
    I've a big problem when i try to save a sales order in CRM via sapgui(the webgui work fine).
    when i save the order the system rise me a short dump OBJECTS_OBJREF_NOT_ASSIGNED.
    this is the dump text.
    Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
    Exception CX_SY_REF_IS_INITIAL
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_BSP_WD_MESSAGE_SERVICE=====CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
    caught in
    procedure "COLLECT_MESSAGES" "(METHOD)", nor was it propagated by a RAISING
    clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "ME->VIEW_MANAGER").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
    Can anybody let me know how solve this issue??
    Best regards
    Marco

    Hi Marco,
    As you have mentioned that the Sales Order is getting saved perfectly from Web UI then there must be some problem with the SAP GUI. You can have look at the call stack to track where exactly the short dump is thrown. If that information is not available, then probably you can put a breakpoint in the function module - CRM_ORDER_MAINTAIN. That is the core One Order API which gets called whenever you save an order in SAP CRM.
    Then, based on your finding you can raise an OSS Message if some SP or Patch are missing in the system.
    Hope this helps.
    Thanks,
    Samantak.

  • Replication of Sales contract from CRM to R/3

    Hi Experts,
    I have a requirement of replicating the created sales contract in CRM to the R/3 system through Middleware in 2007. In the standard way replication of R/3 contract to CRM is only possible. Here the BDOC used in BUS_TRANSACTION_MESSAGE and there is no mapping modules present for CRM to R/3.
    Is it wise to create a custom adapter and use the fm CRM_BUS_MESSAGE_R3_UPLOAD_SRV as the mapping module and enhance the BADI CRM_BUS20001_R3A?
    Please throw me some light on how to proceed with the development.
    Yours answers are greately appreciated!!
    Regards,
    Suthagar.

    Hi Kai,
    Its the normal sales contract with the Pricing aggreements. In SAP help, I found a note saying Note that you cannot download CRM contracts to the SAP ECC system
    please find the link [http://help.sap.com/saphelp_crm60/helpdata/en/7a/e486398dcfd74fe10000000a11402f/frameset.htm], the note can be found in Data exchange for sales contract under the Sales contracts.
    Also on the transaction R3AC1 with the sales contract type, the mapping from CRM to R/3 is blank.
    If it is possbile to replicate from CRM to R/3, please let me know the steps to acheive it.
    Thanks for your help.
    Regards,
    Suthagar.

  • How to make a production order type default for a Plant.

    Hi All,
    I want to know the setting to make production order type ZP01 default for a plant so that when I create a production order using CO01 for that particular plant, it should always use ZP01 as order type?

    Hello Friend,
    One more method is to achieve this is by using Production Scheduling Profile. In transaction OPKP, for your Plant create a new production scheduling profile or use the existing one created in your plant. Inside the production scheduling profile, in order type section, for make to stock field, maintain the value as ZP01 (which you want to come automatically all the time while creating the order by co01) and save.
    Now assign this production scheduling profile in material master of all Semifinished and Finished materials.
    Now create new production order by co01. On initial screen of this transaction give only material code and production plant and enter (don't give anything in order type field).
    After giving material code and production plant, press Enter. After pressing enter system will take you inside the production order .
    Check here by default system will take order type as ZP01.
    Check and Confirm.

  • Creating Distribution List in CRM 2007

    Hiya
    Could somebody please help, is there a way to create Distribution List in CRM for a list of emails, contact from the contacts list.
    Thanks in anticipation.
    Regards
    Ranjeet

    Hello Ranjeet
    Transaction code SO23
    X Shared distribution lists
    Name : ZXXXX
    Title : XXXXX Mail Distribution
    Don't enter anything in the Folder field.
    Folder : Click the down arrow
    Next screen :
    Folder Name : ZXXXX
    Folder Title : Mailing address
    Folder Area : Shared
    Click Create Folder
    Next screen :
    Indexing : Tick
    Specify the 'Retention period of a document in this folder (days)'.
    Choose the 'Folder access authorization'.
    Finish, click the Enter button.
    Click the tabstrips 'Distri. list content' to type in your mailing list.
    Save your entries.
    Finally, test it by sending a mail via the distribution list ZXXXX.
    Regards
    Shikha

  • How to creat Action Profiles in CRM

    Hello Experts,
    Can any one guide me how to create Action Profiles in CRM for attaching the smartform ????
    Regards,
    Amol Tambe.
    SAP CRM Technical Consultant.

    TR: SPRO --> IMG -->Customer Relationship Management -->Basic Functions -->Actions -->Actions in Transaction >Change Actions and Conditions>Define Action Profiles and Actions
    Best Regards,
    Vishant

  • How to create a segement in we31 for an Idoc

    Hi,
    How to create a segment in we31 for an IDOC . I tried its showing an error Name range violation: Name not permitted in customer system

    Hello,
    I have created a customised IDOC scemnario and have a document designed by me with all the minute steps and with screen shots.
    Please have a look at http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
    I am ready to mail it if you can provide email.
    thnx
    ==============================
    Other helpful links
    http://www.sapgenie.com/whitepapers/ale.htm
    http://www.sapgenie.com/ale/index.htm
    http://www.sappoint.com/abap.html
    http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEHR/CABFAALEHR_ALE_QS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECPCA/ECPCA_ALE_154.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

  • Error while creating sales order for material with another DIVISION

    Hello Friends,
    I have a problem with my sales order creation.
    I have defined a new sales area 0010 / 10 / 01. I have the sales order type assigned to this sales area. (in VOV8 for the sales order type, in the 'General Control' the 'item division' is flagged.
    Now, I have created the sold to party XYZ with all the partner functions defaulted same as the sold to party for the sales area 0010 / 10 / 01.
    NOW, I have the material ABC with the DIVISION 10 in the basic data. I have extended the material to my sales org & dist. channel & plant.
    Now, while creating the sales order for my sales area 0010 / 10 / 01 , I enter the sold to party XYZ - it is OK. But when I enter the material ABC, I get the error - "SHIP TO PARTY IS NOT DEFINED FOR SALES AREA 0010 / 10 / 10"
    Please help to resolve the issue.
    Edited by: Vivek on Aug 13, 2009 9:04 AM

    Hi
    Common division for Material Master data will not work
    Because in the material master Division is a field not an organizational unit
    Means when you create MMR you will give sales org, DC, Plant  as organizational units and then enter but not division
    Division is a field maintained in basic data and sales org data 1
    This is the reason in t code you will find in t code VOR2 Common division only customer and conditions but not materials
    But in t code VOR1 Common DC ,customer  conditions and materials all there are available (you can check these t codes)
    Coming to your issue Item div is clecked in your order type
    This means the division in MMR has the priority or control for that order type
    Your header division is 01 ( taken from customers sales area) and item division is 10 (taken from MMR as per your post)
    So it differs
    To process this order with Item div is clecked in your order type you need to extend your Sold to party ABC to the sales area 0010/10/10 (the sales area where the division of the material falls)
    or alternatively
    There should be a  customer say DEF created in sales area 0010/10/10 who will be a ship to party ( your error is also the same)
    for your ABC  that is sold to party in sales area 0010/10/01 where the order is registered
    Hope yopu are getting it
    ABC in sales area 0010/10/01 will have  or should have ship to paty DEF  in sales area 0010/10/10 
    or
    ABC should operate in in sales area 0010/10/10  too
    If item division is not ticked then these are not necessary as the header division 01 will be valid for all items and syatem will not look MMR at all for division
    Regards
    Raja

  • Error: Validation failed for the field - Status While creating Sales Order

    Hi,
    I am getting an error while trying to create sales order header.
    I have tried using provided in the metalink as well but it still doesn't seem to work.
    I am on R12.1.1
    Can somebody help me out on this?
    The code is
    set serveroutput on
    DECLARE
    l_header_rec OE_ORDER_PUB.Header_Rec_Type;
    l_header_rec1 OE_ORDER_PUB.Header_Rec_Type;
    l_line_tbl OE_ORDER_PUB.Line_Tbl_Type;
    l_line_tbl1 OE_ORDER_PUB.Line_Tbl_Type;
    l_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type;
    l_header_adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
    l_line_adj_tbl OE_ORDER_PUB.line_adj_tbl_Type;
    l_header_scr_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
    l_line_scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
    l_request_rec OE_ORDER_PUB.Request_Rec_Type ;
    l_return_status VARCHAR2(1000);
    l_msg_count NUMBER;
    l_msg_data VARCHAR2(1000);
    p_api_version_number NUMBER :=1.0;
    p_init_msg_list VARCHAR2(10) := FND_API.G_FALSE;
    p_return_values VARCHAR2(10) := FND_API.G_FALSE;
    p_action_commit VARCHAR2(10) := FND_API.G_FALSE;
    x_return_status VARCHAR2(1);
    x_msg_count NUMBER;
    x_msg_data VARCHAR2(100);
    p_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC; 
    p_old_header_rec OE_ORDER_PUB.Header_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_REC;
    p_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
    p_old_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type := OE_ORDER_PUB.G_MISS_HEADER_VAL_REC;
    p_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
    p_old_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_TBL;
    p_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
    p_old_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_VAL_TBL;
    p_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
    p_old_Header_Price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_PRICE_ATT_TBL;
    p_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
    p_old_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ATT_TBL;
    p_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
    p_old_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_ADJ_ASSOC_TBL;
    p_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
    p_old_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_TBL;
    p_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
    p_old_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_HEADER_SCREDIT_VAL_TBL;
    p_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
    p_old_line_tbl OE_ORDER_PUB.Line_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_TBL;
    p_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
    p_old_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_VAL_TBL;
    p_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
    p_old_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_TBL;
    p_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
    p_old_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_VAL_TBL;
    p_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
    p_old_Line_Price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_PRICE_ATT_TBL;
    p_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
    p_old_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ATT_TBL;
    p_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
    p_old_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_ADJ_ASSOC_TBL;
    p_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
    p_old_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_TBL;
    p_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
    p_old_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LINE_SCREDIT_VAL_TBL;
    p_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
    p_old_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_TBL;
    p_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
    p_old_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type := OE_ORDER_PUB.G_MISS_LOT_SERIAL_VAL_TBL;
    p_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type := OE_ORDER_PUB.G_MISS_REQUEST_TBL;
    x_header_val_rec OE_ORDER_PUB.Header_Val_Rec_Type;
    x_Header_Adj_tbl OE_ORDER_PUB.Header_Adj_Tbl_Type;
    x_Header_Adj_val_tbl OE_ORDER_PUB.Header_Adj_Val_Tbl_Type;
    x_Header_price_Att_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
    x_Header_Adj_Att_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
    x_Header_Adj_Assoc_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
    x_Header_Scredit_tbl OE_ORDER_PUB.Header_Scredit_Tbl_Type;
    x_Header_Scredit_val_tbl OE_ORDER_PUB.Header_Scredit_Val_Tbl_Type; 
    x_line_val_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
    x_Line_Adj_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
    x_Line_Adj_val_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
    x_Line_price_Att_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
    x_Line_Adj_Att_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
    x_Line_Adj_Assoc_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
    x_Line_Scredit_tbl OE_ORDER_PUB.Line_Scredit_Tbl_Type;
    x_Line_Scredit_val_tbl OE_ORDER_PUB.Line_Scredit_Val_Tbl_Type;
    x_Lot_Serial_tbl OE_ORDER_PUB.Lot_Serial_Tbl_Type;
    x_Lot_Serial_val_tbl OE_ORDER_PUB.Lot_Serial_Val_Tbl_Type;
    x_action_request_tbl OE_ORDER_PUB.Request_Tbl_Type; 
    X_DEBUG_FILE VARCHAR2(100);
    l_line_tbl_index NUMBER;
    l_msg_index_out NUMBER(10);
    BEGIN
    oe_debug_pub.debug_on;
    DBMS_APPLICATION_INFO.set_client_info (121);
    dbms_output.enable(1000000);
    fnd_global.apps_initialize(2787,50703,660); -- pass in user_id, responsibility_id, and application_id
    oe_msg_pub.initialize;
    oe_debug_pub.initialize;
    MO_GLOBAL.init('ONT');
    X_DEBUG_FILE := OE_DEBUG_PUB.Set_Debug_Mode('FILE');
    oe_debug_pub.SetDebugLevel(5); -- Use 5 for the most debuging output, I warn you its a lot of data
    dbms_output.put_line('START OF NEW DEBUG');
    --This is to CREATE an order header and an order line
    --Create Header record
    --Initialize header record to missing
    l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
    l_header_rec.pricing_date := SYSDATE;
    l_header_rec.sold_to_org_id := 2096;
    l_header_rec.ordered_date := SYSDATE;
    l_header_rec.sold_from_org_id := 121     ;
    l_header_rec.salesrep_id := -3;
    l_header_rec.order_type_id := 1003;
    l_header_rec.operation := OE_GLOBALS.G_OPR_CREATE;
    l_line_tbl_index :=1;
    -- FIRST LINE RECORD
    -- Initialize record to missing
    l_line_tbl(l_line_tbl_index) := OE_ORDER_PUB.G_MISS_LINE_REC;
    -- Line attributes
    l_line_tbl(l_line_tbl_index).inventory_item_id := 124516;
    l_line_tbl(l_line_tbl_index).ordered_quantity := 500;
    l_line_tbl(l_line_tbl_index).ship_from_org_id := 563;
    l_line_tbl(l_line_tbl_index).operation := OE_GLOBALS.G_OPR_CREATE;
    -- CALL TO PROCESS ORDER Check the return status and then commit.
    OE_ORDER_PUB.process_order (
      p_api_version_number => 1.0
      , p_init_msg_list => fnd_api.g_false
      , p_return_values => fnd_api.g_false
      , p_action_commit => fnd_api.g_false
      , x_return_status => l_return_status
      , x_msg_count => l_msg_count
      , x_msg_data => l_msg_data
      , p_header_rec => l_header_rec
      , p_line_tbl => l_line_tbl
      , p_action_request_tbl => l_action_request_tbl
       -- OUT PARAMETERS
      , x_header_rec => l_header_rec1
      , x_header_val_rec => x_header_val_rec
      , x_Header_Adj_tbl => x_Header_Adj_tbl
      , x_Header_Adj_val_tbl => x_Header_Adj_val_tbl
      , x_Header_price_Att_tbl => x_Header_price_Att_tbl
      , x_Header_Adj_Att_tbl => x_Header_Adj_Att_tbl
      , x_Header_Adj_Assoc_tbl => x_Header_Adj_Assoc_tbl
      , x_Header_Scredit_tbl => x_Header_Scredit_tbl
      , x_Header_Scredit_val_tbl => x_Header_Scredit_val_tbl
      , x_line_tbl => l_line_tbl1
      , x_line_val_tbl => x_line_val_tbl
      , x_Line_Adj_tbl => x_Line_Adj_tbl
      , x_Line_Adj_val_tbl => x_Line_Adj_val_tbl
      , x_Line_price_Att_tbl => x_Line_price_Att_tbl
      , x_Line_Adj_Att_tbl => x_Line_Adj_Att_tbl
      , x_Line_Adj_Assoc_tbl => x_Line_Adj_Assoc_tbl
      , x_Line_Scredit_tbl => x_Line_Scredit_tbl
      , x_Line_Scredit_val_tbl => x_Line_Scredit_val_tbl
      , x_Lot_Serial_tbl => x_Lot_Serial_tbl
      , x_Lot_Serial_val_tbl => x_Lot_Serial_val_tbl
      , x_action_request_tbl => l_action_request_tbl
      dbms_output.put_line('OM Debug file: ' ||oe_debug_pub.G_DIR||'/'||oe_debug_pub.G_FILE); 
      oe_debug_pub.debug_off;
      -- Retrieve messages
      FOR i IN 1 .. l_msg_count
      LOOP
       Oe_Msg_Pub.get( p_msg_index => i
        , p_encoded => Fnd_Api.G_FALSE
        , p_data => l_msg_data
        , p_msg_index_out => l_msg_index_out);
       DBMS_OUTPUT.PUT_LINE('message is: ' || l_msg_data);
       DBMS_OUTPUT.PUT_LINE('message index is: ' || l_msg_index_out);
      END LOOP;
    -- Check the return status
    IF l_return_status = FND_API.G_RET_STS_SUCCESS
    THEN
      dbms_output.put_line('Process Order Sucess');
      dbms_output.put_line('new Header id:' || l_header_rec1.header_id);
    ELSE
      dbms_output.put_line('Failed');
    END IF;
    Commit;
    END; Regards
    knick

    Kinck
    The same script worked for me in vision (R12.1). You may have issues with your defaulting of a number of attributes that you are not passing in the API (like price list, line type and so on). You may want to check them.
    Thanks
    Nagamohan

  • User Exit to check whether chapter id for Material and Plant combination is maintained while creating sales order

    Hello all,
    my requirement is, system should give error message while creating sales order, if chapter ID is not maintained for a material and plant combination.
    please suggest the user exit.

    Hi
    CASE 1 : All Plants are excisable.
    In Material master , Foreign Trade data tab-  mentioned Control code field mandatory. ( i.e nothing but Chapter ID)
    CASE 2 : Few Plants are excisable
    In the Case 2 you need to go for Enhancement
    Program Name : MV45AFZB 
    User Exit:            USEREXIT_CHECK_VBAP ( Item Level Check )
    By using above user exit you write a logic with the help of ABAPer
    Plant and Chapter ID combination table : J_1IMTCHID

  • Using BAPI_ACTIVITYCRM_CREATEMULTI for creating sales order in CRM

    Hello Experts,
    I am creating a sales order using BAPI_ACTIVITYCRM_CREATEMULTI, But I am getting the following errors:
    1. Reference Object Type (ORGMAN) not allowed
    2. Reference Object Type (PARTNER) not allowed
    3. Incomplete interface data - No reference specified
    4. Item was not found
    Can you please help me with the mandatory fields, that has to be filled in the BAPI, and do I need to use Commit BAPI after this BAPI.
    Please I am in critical postion,
    Now I am able to create a sales order there is no data it like the partner number and Item.May be I am missing some important fileds.
    Please help.
    Thanks,
    Suma
    Edited by: Suma B on Aug 8, 2008 1:05 PM

    Hi,
    I am passing data using SE37 T-Code.
    I was told by the fucntioal guys that GUID will be generated by CRM, so we dont need to send that as an input.
    Still facing the same error...
    These are my input fields:
    REF_HANDLE
    REF_GUID
    R
    OBJECTNAME
    LOGICAL_KEY
    FIELDNAME
    C
    |
    0000000000
    ORDERADM_H
    PROCESS_TYPE
    0000000000
    ORDERADM_H
    POSTING_DATE
    0000000000
    ACTIVITY_H
    CATEGORY
    0000000000
    ACTIVITY_H
    PRIORITY
    0000000000
    ACTIVITY_H
    DIRECTION
    0000000000
    PARTNER
    000000000022XXXXXXX
    REF_PARTNER_FCT
    0000000000
    PARTNER
    000000000022XXXXXXX
    REF_PARTNER_NO
    0000000000
    PARTNER
    000000000022XXXXXXX
    PARTNER_FCT
    0000000000
    PARTNER
    000000000022XXXXXXX
    PARTNER_NO
    0000000000
    ORGMAN
    DIS_CHANNEL
    0000000000
    ORGMAN
    DIVISION
    0000000000
    ORGMAN
    SALES_ORG
    0000000000
    ORDERADM_I
    PRODUCT
    0000000001
    B
    SCHEDLIN
    00000000000000000000000000000000
    QUANTITY
    |
    This is error log:
    T
    ID
    NUM
    MESSAGE
    LOG_NO
    LOG_MS
    MESSAGE_V1
    MESSAGE_V2
    MESSAGE_V3
    MESSAGE_V4
    PARAMETER
    ROW
    FIELD
    SYSTEM
    |
    W
    CRM_ORDER
    004
    Referenced object type (ORGMAN) not allowed
    $000001
    000001
    ORGMAN
    ORDER
    0
    CR5CLNT100
    W
    CRM_ORDER
    004
    Referenced object type (PARTNER) not allowed
    $000001
    000002
    PARTNER
    ORDER
    0
    CR5CLNT100
    W
    CRM_ORDER
    005
    Incomplete interface data - No reference specified
    $000001
    000003
    ORDER
    0
    CR5CLNT100
    E
    CRM_ORDERADM_I
    006
    Item  was not found.
    $000001
    000004
    ORDER
    0
    CR5CLNT100
    E
    CRM_ORDER
    005
    Incomplete interface data - No reference specified
    $000001
    000005
    ORDER
    0
    CR5CLNT100
    S
    CRM_MESSAGES
    005
    A log has been generated for single document
    $000001
    000006
    MESSAGES
    0
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Sold-To Party
    $000002
    000001
    Sold-To Party
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Ship-To Party
    $000002
    000002
    Ship-To Party
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Bill-To Party
    $000002
    000003
    Bill-To Party
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Payer
    $000002
    000004
    Payer
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Sold-To Party
    00000000000000047612
    000001
    Sold-To Party
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Ship-To Party
    00000000000000047612
    000002
    Ship-To Party
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Bill-To Party
    00000000000000047612
    000003
    Bill-To Party
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    E
    COM_PARTNER
    119
    Enter   Payer
    00000000000000047612
    000004
    Payer
    PARTNER
    0
    PARTNER_NO
    CR5CLNT100
    |
    Thanks,
    Suma

Maybe you are looking for