AP7 Pricing Userexit - what's comm struct / doc for fields to formula

Hi Everyone,
I need to define some attributes used in my Pricing Userexit / formula (TC=/n/sapcnd/ueass). My questionis is what's the field name (i.e. for Product, Qty) I need to pick/assign to the formula.  Do I need to do the same for Implementation attributes,? but no dropdown box for me to select, just enter the same name as formula field?
Any communication structure or documentation for these attrubutes / fields?  Please advise.
Thanks, Jin
Thanks alot in advance, Jin
Edited by: Jin Freda on Oct 31, 2008 9:55 PM

I have to close it

Similar Messages

  • JCo Connection / RFC in Pricing Userexit

    Hi Experts,
    Need your help: I have a requirement to make a RFC call in IPC Pricing Userexit.  First I made a simple test java class to make RFC call and run it locally without any problem. then I copy the same code to the Userexit, but it failed on the 1st statment JCO.createClient(.....).  Do I need to add a different JAR file to make JCo Connection work in the Userexit? Any advise or documentation?.
    Thanks, Jin
    Here is the error message:
    Message: document not existing
    --> com.sap.spe.document.rfc.DocIllegalArgumentException: document 49149C3E59925857E10000000A02901D not existing
    at com.sap.spe.document.rfc.DocHandlerAdapter.appendProtocolLine(I[Ljava/lang/Object;)V(DocHandlerAdapter.java:123)
    at com.sap.spe.document.rfc.GetPricingDocumentInfo.handleDocRequest()V(GetPricingDocumentInfo.java:73)
    at com.sap.spe.document.rfc.DocHandlerAdapter.handleRequest()V(DocHandlerAdapter.java:72)
    at com.sap.spe.base.util.jco.HandlerAdapter.handleRequest(Lcom/sap/vmc/RFCContainer/Call;)V(HandlerAdapter.java:103)
    at com.sap.vmc.remserver.RFCDispatcher.privHandleRequest(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:895)
    at com.sap.vmc.remserver.RFCDispatcher.handleRequest(Lcom/sap/conn/jco/JCoFunction;)V(RFCDispatcher.java:673)
    at com.sap.conn.jco.rt.JCoServer.dispatchRequest(Lcom/sap/conn/jco/rt/AbapFunction;)V(JCoServer.java:1605)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(Lcom/sap/conn/jco/rt/JCoServer;Ljava/lang/String;)V(MiddlewareJavaRfc.java:2387)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(Lcom/sap/conn/jco/rt/JCoServer;Ljava/lang/String;)V(MiddlewareJavaRfc.java:1694)
    at com.sap.conn.jco.rt.JCoServer.listen()V(JCoServer.java:1375)
    at com.sap.conn.jco.rt.JCoServer.run()V(JCoServer.java:1299)
    at com.sap.vmc.remserver.RfcServer.run()V(RfcServer.java:386)
    at java.lang.Thread.startup(Z)V(Thr
    Thanks, Jin

    Hello Jin,
    IPC does make calls to CRM . To do so it maintains a JCo connection. We got to leverage this connection object and make calls to our RFC. We can use the get_current_connection(); from connection_factory.
    import com.sap.mw.jco.JCO;
    import com.sap.sce.engine.ddb_inst;
    import com.sap.sxe.db.*;
    import com.sap.sxe.db.imp.rfc.*;
    import com.sap.mw.jco.IFunctionTemplate;
    import com.sap.mw.jco.IRepository;
    // For the default connection
    JCO.Client crmJCO = null;
    try{
    / RFC and JCO connection to CRM
         connRFC cRFC = (connRFC)connection_factory.get_current_connection();
         crmJCO = cRFC.getIdleConnection();
    }catch(Exception e){
         log_api.log_write_msg("LOG1", "LOG2",1,
           "Error establishing JCO connection to CRM: "+ e);
    // Now for the BAPI (RFC calls)
    try{
         IRepository repository = JCO.createRepository
                               ("<my BAPI RFC module>", crmJCO);
         IFunctionTemplate ftemplate = repository.getFunctionTemplate
                              ("<my BAPI RFC module>");
         JCO.Function bapiFunc= new JCO.Function(ftemplate);
    // Set your IMPORT, EXPORT, TABLE parameters here
    // Call the JCo function
         crmJCO.execute(bapiFunc);
    // Process the output.
    }catch(Exception e){
         log_api.log_write_msg("LOG3", "LOG4",1,
           "Error calling BAPI "+ e);
    /// DO NOT FORGET TO CLOSE ***+++ MUST DO +++***
    }finally{
         if(crmJCO != null)
              JCO.releaseClient(crmJCO);
    Hence this is using standard connection, no need for any additional jars.
    Easwar Ram
    http://www.parxlns.com

  • Error when building the Java pricing userexit manual code

    I went throught the manual for the pricing userexit manual... it tells you to ignore the errors when you do an ant build but I want to remove all the errors since they dont let the rest the code compile.... where are the jars for these errors: 
    [javadoc] C:\DEV\PRC_UE_CUSTOMER\lib_src\src\com\sap\spc\document\DocumentConstants.java:16: package com.sap.vmc.logging does not exist
         [javadoc] import com.sap.vmc.logging.Category;
         [javadoc]                            ^
         [javadoc] C:\DEV\PRC_UE_CUSTOMER\lib_src\src\com\sap\spc\document\DocumentConstants.java:26: cannot resolve symbol
         [javadoc] symbol  : class Category
         [javadoc] location: class com.sap.spc.document.DocumentConstants
         [javadoc]     public static final Category CATEGORY = Category.getCategory(Category.APPLICATIONS, "/AP/SPC/Document");
         [javadoc]                         ^

    See the [SAP note 809820 - Userexit concept for pricing|https://service.sap.com/sap/support/notes/809820]
    Use ZIP file the attached to the above note - PRC_UE_CUSTOMER_V105.zip
    ZIP file contains an Eclipse .project file that has the required build path. If you read the documents carefully, it does refer this project file.
    <?xml version="1.0" encoding="UTF-8"?>
    <classpath>
         <classpathentry kind="src" path="src"/>
         <classpathentry sourcepath="lib_src/src" kind="lib" path="lib_api"/>
         <classpathentry kind="lib" path="lib_vmc_api/base_services_stripped_api.jar"/>
         <classpathentry kind="output" path="bin"/>
    </classpath>
    Again read the documents thoroughly. They are neither fictions nor non-fictions, but technical documents written with care. So, we must also read them with care. If we don't follow them, then it is time to engage someone who does. )
    BTW, coming back to the Java basics - One must have a class and source files to debug. You won't get a class file unless it is compiled. The Java file won't compile correctly if it has syntax / reference errors. Unfortunately or fortunately, all these apply to the IPC java userexit development as well.
    Easwar Ram

  • What's the best app for editing and viewing office doc's

    What is the best App for editing and viewing office doc's, that will be compatable with IPhone 5S and Air pad?

    Search the app store, find one that you like and that works for you.

  • I downloaded lion but now I cannot access my word and excel docs for work.  What can be done easily to open all my files?

    I downloaded lion but now I cannot access my word and excel docs for work.  What can be done easily to open all my files?

    tamanacoazur wrote:
    Have not a clue if this a LION problem or Microsoft problem.  My gut says Microsoft as they acknowledge the problem in their support section.  Their solution:  Open files with previous version of Word.  That is completely unacceptable as a solution in my opinion.  Why would have I ever bothered to upgrade to 2011 if I had known I need to keep a version of 2008 running on my computer. 
    Honestly I don't know if it's a Lion or MS problem eihter. I have been using Lion for many months with Office 2011 with no problems though.The earliest version I had on my machine was 2008 and 2011 opened those files with no problems at all. As Dave mentioned earlier he opens Office 2004 files all the time with 2011.
    One thing you might want to do is restart the computer while holding down the Option key then select the Restore Volume and run Disk Utility and repair the Disk Permissions on the HD. Run DP at least 2x.

  • What happened to my doc?

    I was working on a cover letter in Pages when i either accidentally typed a hotkey, or clicked on something. I dont know what happened but my doc now looks rather strange. I'm very new to Apple, iWork and Pages, so I don't know my way around this software yet. I tried to find a solution for this bizarre issue, but without fully understanding the problem, I'm stuck. I decided my only hope was to post a screenshot here and hope someone could explain to me what I've done.
    I replaced the actual text with gibberish due to the personal information included in the original doc. Can anyone explain these dashes or what is going on here? I want my doc to go back to normal.

    It looks like it is in outline mode. Try clicking the outline icon in the toolbar to toggle it off.

  • How do i remove the 17 errors that come with the pricing userexit manual at

    how do i remove the 17 errors that come with the pricing userexit manual attached code...

    Try connecting the phone to the computer in "data storage" or "data transfer" mode, then open the memory card folder in Windows Explorer, and search the sounds there. If you can't see them, go to "Tools>Folder Options>View>Files and Folders>Hidden files and folders" and select "Show hidden files and folders". But I think that it would be a lot easyer just to remove them from the playlist manualy.
    Crossing bridges far ahead of the crowd.

  • Can I know what is "Commit" after failover to Azure ?

    Can I know what is "commit" after failover to Azure ?
    I want to know "Commit" button of protected items.
    SETUP RECOVERY: [ Between an on-premisese Hyper-V site and Azure ]
    After failover from on-premis Hyper-V site to Azure, Protected item show "Commit" button.
    "Commit" Jobs include "Prerequisite check"  and "Commit".
    Regards,
    Yoshihiro Kawabata

    In ASR Failover can be thought to be a 2 Phase Activity.
    1) The Actual Failover where you bring up the VM in Azure using the latest recovery point available.
    2) Committing the failover  to that point.
    Now the question in your mind will be why do we have these 2 Phases. The reason for this is as follows
    Lets say you have configured your VM to have 24 recovery points with hourly App Consistent Snapshots. When you failover ASR automatically picks up the latest point in time that is available for failover (day 9:35 AM). Say you were not happy with that recovery
    point because of some consistency issue in the application data, you can use the Change Recovery Point button(Gesture) in the ASR Portal to choose a different recovery point (say an app consistent snapshot from 9:00 AM that day) to perform the failover.
    Once you are satisfied with the snapshot that is failed over in Azure you can hit the Commit Button. Once you hit the commit button you will not be able to change your Recovery Point.
    Let me know if you have more questions.
    Regards,
    Anoop KV

  • What is a billing Doc?

    Hi people,
    What is a Billing Doc?
    Is it similar to Sales Order ?
    If yes ,please tell me the use and procedure to create a Billing Doc.

    Dear Shashank,
                          Billing Document is a broad term which can be a credit memo, debit memo, proforma invoice based on order or based on delivery and also a regular invoice.
    For example let us look at on sales cycle :
    order -> delivery -> Invoice.
    credit memo, debit memo are self explanatory by terms and an invoice is what you give the customer based on which he makes the payment to you.
    A sales order is prepared on a Sold to party where as an invoice is done on a Bill to party. And just use T. Code <b>VF01</b> here you give the delivery document number which you want to invoice if it is delivery related billing or sales order number if it is Order related blilling.
    Hope you have now a fair idea Else please get back.
    Reward if you find the explanation useful.
    Thanks & Regards
    Sadhu Kishore

  • 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

  • Issue using Comma as Delimiter for SelectManyChoice

    Hi,
    Jdeveloper version 11.1.1.6 .
    I have implemented this simple usecase which is not working. Create a VO in Model and expose it through AM . Now drag and drop ViewObject as SelectManyChoice.
    Run the page...
    It runs perfectly fine. When you select more than one value in selectManyChoice , they are shown in the inputField with a delimiter ";" [ semicolon ]. I have a requirement to change it to comma "," .
    So there is a property delimiter in ListBinding in pageDef. I tried modifying that property to #{','} and page stopped loading.
    How to specify your custom delimiter in SelectManyChoice component    ?
    Thanks,
    Rajdeep

    Hi Frank,
    So I assume this requirement then is for cosmetic reasons?
    You are correct that requirement is for cosmetic change.
    As far as I know changing the delimiter is not possible ( I checked the skinning docs and no resource String is provided).
    So what is the delimiter property for ? .. is it there for future enhancement or does something.
    Note that he actual value is returned as an array of index or object (dependent on how you implemented this)
    My implementation is simple . I just drag and drop a VO as select many choice. And tried to place comma in delimiter property of the ListBinding created in pageDef.
    Thanks,
    Rajdeep

  • Canceling a billing doc for which accounting doc not yet generated

    Hello,
    I have strange issue in canceling billing doc. What happened user created Intercompany billing doc IV against a delivery and accounting doc also released to FI. After that he found that value in that IV doc is not correct so he went and cancelled that doc IV and he created internal credit memo IG .But for this IG the accounting doc not generated due to FI period closing. Because the IV is created in the month of Oct and IG is created in the month of Nov'07.Due to this issue Accounting document not generated for this IG doc.
    But unfortunately by mistake he went cancelled the IG doc and it created IV again. Now what happened both IG and new IV created are showing in cancelled status. This is because if we cancel a billing doc for which accounting doc not created, then both doc will turning into cancelled status in doc flow. This is confirmed similar situation in my quality box and confirmed.
    Now can anybody come across this kind of issue and tell me what is the best approach to handle this kind of situation.
    Thanks
    Mathi

    Hi Nina
    As you are doing Delivery and then billing  with the service item category ZTAD , so go to VOV7 and check wheather the Billing Relevance ( Delivery related billing ) has been maintained or not .
    Also check wheather in VTLA & VTFL copy controls  ,  ZTAD item category has been maintained or not
    Regards
    Srinath

  • What technical components are needed for integration of SAP BI and BO?

    Hello,
    What technical components are needed for integration of SAP BI and BO?

    Hi,
    you need to setup a BOBJ server (eg. BusinessObjects Enterprise XI 3.1 or BO Edge 3.1) and then install the BusinessObjects integration Kit for SAP on the same machine your BOBJ server runs.
    In order to build reports you can either use Crystal Reports (eg Install Crystal Report Designer 2008 V1 if you have an XI 3.1 server installed), WebIntelligence (Install the Business Objects XI 3.1 Client Tools in order to be able to build universes), BusinessObjects Voyager or XCelsius. Please note that you have to always install the BOBJ integration Kit for SAP (should be the same version as your server and client installation) on your clients AFTER you installed one or more of the above client tools.
    Please take again a look at the following link for more detailed information (from Ingo) on this:
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a00ee3b2-5283-2b10-f1bf-8c6413e0898f]
    Regards,
    Stratos

  • What are the Things required for BI 7.0 Implementation project

    Hi Friends,
                      Can any one suggest me
    1.What are the Things required for BI 7.0 Implementation project?
    2.System Configurations & Hardware Components?
    3. Any additional steps...
    plz suggest me.
    Regards

    Hi lakshmi,
    http://csc-studentweb.lrc.edu/swp/Berg/articles/PM_2006_upgrade_NW2004s_Bjarne_Berg_v12.ppt#426,3,Why Upgrade u2013 end of supportu2026
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b8d163a7-0301-0010-d9b0-98f692ea3c60
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881
    https://wiki.sdn.sap.com/wiki/x/JYk
    Check the following links.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    check the following
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    business content
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    https://websmp203.sap-ag.de/co
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm

  • What are the table names for CRM and APO?

    hi friends,
    what are the table names for CRM and APO?
    Regards
    suneel.

    hi Suneel,
    check in crm forum
    Re: SAP-CRM Tables
    BUT051 BP Relationship: Contact Person Relationship
    Similar to BUT050 , additionally contains Contact Person’s Address data
    BUT0BK Business Partner: Bank Data & Details
    BP Number, Bank Key, Bank Country Key, Bank Account Number
    BNKA Bank Master Data
    BUT100 BP: Roles
    ADR2 Telephone Numbers (Business Address Services)
    ADR6 SMTP Numbers (Business Address Services)
    Contains Email – Id of the BP.
    ADRC Addresses (Business Address Services)
    BP’s Complete Address Details- City, Country, Post Code, District, Street, Title No Etc
    TSAD3T Table containing the Title text against a Title No.
    COMM_PRODUCT Master Table for Product
    CRMM_BUAG Master table for Business Agreement
    CRMM_BUAG_H Header Data for Business Agreement such as Tax Category, Tax Characteristic, Form key, Business Agreement Class. Data in this table correspond to ISU CRMD_ORDERADM_H Contains the Header Information for a Business Transaction.
    Note:
    1. It doesn’t store the Business Partner
    responsible for the transaction. To
    get the Partner No, link it with
    CRM_ORDER_INDEX.
    2. This table can be used for search
    based on the Object Id(Business
    Transaction No).
    CRMD_CUSTOMER_H Additional Site Details at the Header Level of a Business Transaction
    CRMC_PROC_TYPE Master table Business Transaction Type
    CRMC_PARTNER_FCT Definition of Partner Functions
    SCPRIOT Priorities for Activities with priority text.
    CRMC_PROC_TYPE_T Text for a transaction type
    CRMC_ACT_OBJ_T Objective Number and Text for Activities
    TJ30T All the status code and text
    CRMC_PR_ASSIGN : Transaction Type and its Transaction Type Object.
    IBIB : Installed Base/Ibase
    IBIN : Installed Base Components
    COMM_PRODUCT : Products
    CRMC_T077D : customer account groups
    CRMD_ORDERADM_H (for header) CRMD_ORDERADM_I (Item data)
    CRMD_ORDERADM_H Business Transactions CRM
    CRMD_ACTIVITY_H Activity
    CRMD_OPPORT_H Opportunity
    BUTOO : Customer details
    BUT001 BP: General data II
    BUT100 BP: Roles
    BUT150 BP relationship: Attribute table (test
    different
    BUT_HIER_TREE Business Partner Group Hierarchy
    CDBC_T_PRODUCTID Mapping: Product Id
    CDBD_ORGMAN Business transaction - organizational unit -
    set
    COMC_PRODUCT General Product Settings
    COMC_R3_FIELDS Assignment of R/3 material master fields to
    CFOP
    COMM_CATEGORY Category
    COMM_CFGMAT Basic Data for Materials
    COMM_HIERARCHY Category Hierarchy
    COMP_TYPES Hierarchy Tool: Comparison Type Check
    Table
    CRMC_CPRICPROC Customer Pricing Procedures
    SMOKVBEZ15 Assignment employees to positions
    CRMMLSGUID: GUID entry (should match GUID in CRMPRLS)
    CRMM_BUT_CUSTNO : Also GUID table (GUID here should match GUID in R/3 table CRMKUNNR)
    SMOFSUBTAB : Mapping & Parameters
    SMOFDSTAT : Download Monitor (R4AM1)
    SMOFFILTAB : Filters (Should match filters in R3AC1 & R/3 Table CRMFILTAB)
    SMOFOBJECT Definition of Objects for Download
    SMOFOBJPAR Parent Objects of an Object in Table
    SMOFPARSFA Middleware Parameter
    SMOFQFIND Queue Finder Table for MW-Queue finder
    SMOFTABLES Definition of Tables for Download

Maybe you are looking for