CRMXIF_PARTNER_SAVE_M IDOC customization

Hi All,
I need to filter the XIF Business Partner Master IDOC based on certain vaues like create by,changed by fields.
For that I have customized the basic IDOC type to 'YCRMXIF_PARTNER_SAVE_M01' with required segments and assigned it to Message Type 'CRMXIF_PARTNER_SAVE_M'.
I have configured Partner profile and outbound parameters with this message type and basic IDOC type.
IDOC's of type YCRMXIF_PARTNER_SAVE_M01 are getting distributed for new/changed BP's.
Now I need to know which function module it uses to generate/distribute IDOC's,so that I can customize that function module and write the filter logic inside that.
is this the better way to filter IDOC distribution to external clients like XI.if there is any other way to do this please advice me.I would appreciate that.
Thanks in advance.
Thirumala.

Hi Thirumala,
As per my knowledge all CRMXIF IDoc basic types are generated and you will not be able to create an IDoc extension. I suppose you have created a copy of that IDoc type. For CRMXIF IDocs the ideal way is to use BDFG transaction to re-generate the IDoc. CRMXIF_PARTNER_SAVE is the function module that needs to be used in BDFG. If you want to filter values based on certain fields you can implement the BAdi  CRMXIF_PARTNER_MAP for partners. This BAdi is called in function module CRMXIF_PARTNER_MAP_FROM which is called in FM CRMXIF_PARTNER_SAVE.
Let me know if this was helpful!
Cheers,
Mahesh

Similar Messages

  • Regarding SAP SI

    Wt is RICEFs? I need some informations or related site, how to develop this one?
    Thanks
    Girish

    Hi,
    R - Reports
    R refers report programming. Of course, firstly classical report programming, WRITE statement; then it means ALV programming with either ALV function modules or ABAP objects.
    I - Interfaces
    Interfaces are ALE / IDOC developments. Not only development, ABAP programming for IDOCs, also IDOC customization, management. I think it might refers EDI too.
    C - Conversion
    I think conversions means BDC programming, batch input function modules, BDCDATA structure, CALL TRANSACTION. Maybe conversion specifically refers conversion programs for standard batch input programs. Even we can say it refers LSMW.
    E - Enhancements
    Enhancements are user-exits and the object oriented model of user-exits that is BADIs.
    F - Forms
    Forms are SAPscript forms, SAPscript print programs, and SmartForms.
    Regards,
    Anirban

  • Search customize field/segment in IDoc

    Hi,
    I've have requirement to delete a customize field ZMKOL that belong a append structure Yxxxx in VBAP. By doing that, i need to scan through all the existing IDoc interfaces that using ZMKOL.
    Right now, i do have a list of inbound and outbound interfaces that using in my company.  So could you please advise what is the best way for me to identify field ZMKOL is using in which interface?
    Please comment.

    Since ZMKOL is a custom field, to include it in an IDoc someone had to create a custom segment and extend the IDoc. The custom segments are maintained in WE31. Find out which custom segments have this field and then you'll be able to find which IDocs include these segments.
    Also just do a 'where used' on the field in SE11 - this will most likely find the programs where the field is being populated for the IDocs.
    Do a search on IDoc extension if you need more info.

  • Best way to customize IDOC INVOIC02 (outbound)

    Hello,
    I want to customize the IDOC type INVOIC02 (outbound). Customize means:
    - remove segments
    - change some values
    I tried different ways to achive this, but it does not work as needed. What I tried:
    - IDOC extension: can not be used, because I can not remove segments
    - IDOC view: not possible for INVOIC02 (see sapnote 185445)
    - new IDOC type: I created a new IDOC type and copied all needed segments from INVOIC02. Now I want to use the existing function IDOC_OUTPUT_INVOIC, but it does not work. The IDOC gets status 26 (Syntax error, E1EDK17 does not exist). I do not want to rewrite the existing function. I think this would be the worst.
    - new idea (not tried yet): use the existing INVOIC02 and change, remove segments in the user-exit.
    Can someone help me and maybe give me hint?
    Thanks, best regards
    Andreas

    Hi Sasidhar,
    I am using EXIT_SAPLVEDF_002 now and it works like a charm. Thanks!
    This is my coding right now (maybe it helps someone reading this):
    *&  Include           ZXEDFU02                                         *
    *separate by partner
    CASE control_record_out-rcvprn.
    * Special customer
      WHEN '0000123456'.
    *   get segment
        CASE int_edidd-segnam.
    *     delete segments
          WHEN 'E1EDK17' OR
            'E1EDK23' OR
            'E1EDK28' OR
            'E1EDK29' OR
            'E1EDK14' OR
            'E1EDP03' OR
            'E1EDPA1' OR
            'E1EDP28' OR
            'E1EDP08' OR
            'E1EDP30'.
            DELETE TABLE int_edidd.
        ENDCASE.
    ENDCASE .
    Regards,
    Andreas

  • Clear customize Date field value in workflow using IDOC Script

    hi all
    I have a customize field type is Date with default value is Current date time. At one step of workflow I want to clear the default value of this field with
    <$wfUpdateMetaData("xmPublicDate", "")$>
    But it not effect. The current date time still here
    Do you have any idea about it?
    Thanks!

    hi all
    I have a customize field type is Date with default value is Current date time. At one step of workflow I want to clear the default value of this field with
    <$wfUpdateMetaData("xmPublicDate", "")$>
    But it not effect. The current date time still here
    Do you have any idea about it?
    Thanks!

  • ALE IDoc : Vendor Master : Cremas: Inbound IDocs are bypassing the Customiz

    Hi,
    Create Vendor master inbound IDocs - CREMAS - are overridding the customizing settings.
    For example for a particular vendor group  a number range is set in customizing.
    When we try to create a vendor through XK01 which does not fall in a particular number range as set in customising for a particular vendor group, we get a error message and creation is terminated.
    But if the same vendor is created via standard idoc CREMAS, vendor is created without any errors bypassing the customizing settings.
    So can anybody help me in this. Is there any customising setting that we need to do explicitly for Vendor IDocs. Or any other setting in standard IDoc.
    Thanks in advance.

    Hi,
    1. If your vendor changes should be updated from one system to other system through ALE, we need to active the change pointers.
    2. Change points can be activate through Tcode SALE
    3. After activating change points and your distribution model is ready, you can execute the program RBDMIDOC to genarate the IDOCs.
    4. Normally this program will be executed in the background
    5. And as you said, you have to do some validations before sending IDOCs. For this you can Filters and rules in the DM.
    OR you can write the code in user-exists of outbound posting program.
    Rewards if this info is useful.
    Thanks,

  • How link customize IDOC message type with FM ?

    Hi,
    I have created new IDOC message type ZCOST and FM ZMASTERIDOC_CREATE_COST. (Outbound).
    Please advise how link the message type and FM ? so everytime i am executing BD21 with message type ZCOST the program always calling FM ZMASTERIDOC_CREATE_COST to generate the IDOC.
    Thank You and Best Regards
    Fernand

    HI,
    You need to link Mssage type, IDOC type and the FM (also extension idoc type if exits) in TCODE: WE57 --> go to change mode
    --> then new entries --> even you need to gove the direction inbound/outbound.
    Also you need to create a outbound custom process code in WE41. and link the FM to the process code.
    This process code shold be assigned to the partner profile in we20 in outbound parameters -> so you FM will be picked up qutomatically.
    regards,
    Nazeer
    Edited by: N a z e e r on Jul 14, 2010 3:14 PM

  • Customize the appearance of Content Server pages with hcsf and idoc?

    I've read through the documentation here:
    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e10807/c04_look_nav002.htm
    and can create a simple form using hcsf and idoc.
    Here's what I would really like to do:
    I would like to create very streamlined forms that support the following Content Server functions:
    1. Document Search
    2. Document Checkout
    3. New Document Add
    4. Display of Search results
    What I mean by streamlined is this: no tool bars of any kind, no decorations, just the bare minimum to support the above mentioned functions.
    My questions:
    Is this even possible?
    Are there examples of this anywhere?
    Is there further documentation about using hcsf and idoc to integrate with Content Server functions?
    Thanks in advance for your help,
    Dave

    Dave,
    try adding &coreContentOnly=1 to the end of the URL and see if that does the trick for you.
    This prevents the std_page_begin and std_page_end includes from being executed/displayed which removes the toolbars etc.
    Using profiles and rules you can control the rest of the search and checkin form layout and look/feel.
    If you really want to reproduce standard behavior with forms (e.g. for other specialized purposes) then take a look at Bex's book (http://www.amazon.com/Definitive-Stellent-Content-Server-Development/dp/1590596846)
    or talk to us at Fishbowl as forms and workflows are a specialty of ours - http://bit.ly/b2Ydv6
    we do special forms for business process centric work like BOMs, ECOs, CERs, Contract Management, CapEx etc...
    Warmly,
    Billy Cripe
    Fishbowl Solutions

  • Customization for Change Pointer Mechanism in IDOC Programming?

    Hi,
    Can anyone suggest me that
        We want to Maintain Master and Transactional Data in Different SAP Servers.I want to Send the Master Data to the other Server but before IDOC Creation i need to Display all Created or Changed Master Data then Our endusers will select Specific Master Data then only IDOC will create for that Master Data and Created IDOCs will send to the other SAP Server where Transactional Data is Maintained.
       In Change Poinetr Mechanism it is not possible to see the Created or Changed Master Data before IDOC is going to be Created.But i need to Display the Master Data.
    Please give me an idea to solve this or if you have any solution then send me.

    Hi,
    When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention.  If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen.  Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
    Thanks,
    Mahesh.

  • Error in creation of  PurOrd IDoc

    Hi All,
    I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG  but  when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
    What could be the possible problem?
    Highly appreciate any kind of help.
    Thanks in advance,
    Shweta
    PS: <b><REMOVED BY MODERATOR></b>
    Message was edited by:
            Alvaro Tejada Galindo

    Hi
    Check the Partner Profile in WE20 correctly
    also see the steps for it as per the doc
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    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
    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
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    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
    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
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Regards
    Anji

  • Payment Order (multiple) Idocs need to be downloaded into single file

    Hello Gurus,
    I am able to generate Idocs for Automatic Payment Run in F110 for message type PAYEXT with PEXR2002 idoc type.  However, what I found is the system generates one idoc per vendor for a single payment method. So, for example if I run APP for 50 vendors at a time, 50 different idocs are generated and placed in AL11.  Currently the requirement is to download the idocs into flat file and upload it in Bank's website. I would like to know is there any way to download all the 50 idocs into a single file (ie a single file containing payment run information for all vendors).
    PS: I use CG3Y Tcode to dowload Idoc from AL11 mentioning the directory path but this can allow me to download only one file at a time.
    Any Info regarding this would be appreciated.
    Thanks in advance,
    -Naryanaan-

    Hi
    I'm facing the same problem . Were you able to solve this by heavy customization.
    best Wishes

  • Idoc for materials and service for same contract.

    Dear All
       I have an scope where i have to migrate the data for material and services for the same contract.Is there an Idoc which does it so or otherwise ?Earlier in scope materials contracts have been loaded with the help of idoc type :- PURCONTRACT_CREATE01  and that of Service Contract using Idoc type :- BLAORD03.No customization is however permitted .Tcode for the same is ME32K.
    Regards
    Somnath

    Hi,
    It is not clear to me if you are working with sapscript or smartforms.
    You have only to find a variable which identifies the kind of invoice
    I do not know that variable so i use an example variable
    for sapscript:
    /: IF &VBDKR-FKTYP& = '1'
    /  INVOICE
    /: ELSE
    /  SERVICE ORDER
    /: ENDIF.
    In a smartform you can also do something like that.
    but There you work with conditions (eq, BOOLEAN)
    You have only to find the right variable
    success,
    Gr., Frank

  • Length of IDoc field is cut

    Hello,
    I have the following problem:
    I have a vendor master scenario which means XML File to CREMAS IDoc. The problem is here the phone numer.
    The length of the phone numer is set to max=16 in the IDoc schema. If I have a longer phone number obviously this is no problem in the mapping itself as I do not get an error message there.
    Is this correct? I would have expected an error when I test the message mapping with the "test" tab.
    However the phone number is then cut in the SAP ERP-system after receiving. Is there any way to change this field to accept longer values in the backend SAP ERP system? What are the steps to be done if this is possible?
    Thank you very much for your advise.

    >
    Florian G. wrote:
    > Hello,
    >
    > I have the following problem:
    >
    > I have a vendor master scenario which means XML File to CREMAS IDoc. The problem is here the phone numer.
    > The length of the phone numer is set to max=16 in the IDoc schema. If I have a longer phone number obviously this is no problem in the mapping itself as I do not get an error message there.
    > Is this correct? I would have expected an error when I test the message mapping with the "test" tab.
    >
    XI 3.0 or PI 7.0 doesnt do such a validation on the XSD. So it will not throw any error.
    in PI 7.1 you can force a XSD validation
    > However the phone number is then cut in the SAP ERP-system after receiving. Is there any way to change this field to accept longer values in the backend SAP ERP system? What are the steps to be done if this is possible?
    >
    > Thank you very much for your advise.
    you will have to customize the Idoc in R3to accept more characters than the specified length in the backend SAP

  • IDoc for BP migration is in error on transferring from CRM 4.0 to 7.0

    Hi,
    We have a requirement to migrate Business Partners from CRM 4.0 to CRM 7.0. We are using the message type CRMXIF_PARTNER_SAVE_M for this purpose. The IDocs are generated correctly from CRM 4.0 and carry the correct data. The status of Idoc in CRM 4.0 is set to 03.
    However, on checking in CRM 7.0 system, we found the IDocs to be in error with a status of 51. The IDocs fail validation on the Birthdate field - where first 3 digits are replaced by spaces.
    Any suggestions on how to correct the birthdate field? There are no changes being done to the data during mapping on either the inbound or outbound site.
    Regards,
    Mugdha

    Hello,
    note 915509 (needs to be implemented manually) should solve this issue.
    Best regards,
    Christian

  • LSMW to upload Business Partner through IDOC

    Hello,
    I have requirement to upload Business partner  through IDOC. I am using below message type and IDOC type.
    1:- Message Type :- CRMXIF_PARTNER_SAVE_M
    2:- Basic Type :- CRMXIF_PARTNER_SAVE_M02
    Could you please tell me what configuration I need to do for this? Like creating partner profile, port etc
    Also I need to extend this IDOC segment to take care of my Z fields.
    After extending the IDOC segment do I need to write code in order to update this Z filed or it will be take care and also how to extend existing IDOC.
    If any one have has done this before then please share the logic.
    Kindly help.
    Regards
    Sachin

    Hi,
    Try LSMW with the IDOC method.
    Message type: BUPAFS_FS_CREATE_FRM_DATA2
    Basic type: BUPAFS_FS_CREATE_FRM_DATA201
    You will need to setting for IDOC: port, partner type, etc.
    Manish

Maybe you are looking for