Customer Master Data via a Bapi/ALE

Hello All. I am new to this forum. I have a couple of questions.
What I am trying to do: I have to interface to SAP with Websphere Message Broker which has inbuilt nodes to interface with SAP using BAPI or ALE to send Customer Master Record (create/update/delete)
The questions I have:
1/ Has anyone done this? What did you use BAPI or ALE?
2/ When a Customer Master IDOC is sent to SAP, if successful, a return code is sent back by SAP. This indicates that SAP has received the IDOC successfully. However, our requirement is that we have to know whether the IDOC was successfully posted within SAP. I am of the opinion that this is manual task within SAP and it should not be the function of the middleware layer as its responsibility is only to successfully deliver the IDOC's. I would welcome opinions on this issue. Please let me know If there is a way to determine if the IDOC has been successfully posted in SAP.
3/ Is there anywhere where I can get an XML representation of the Customer Master Record. I want to see the structure and the available fields. How can I get this info from SAP?
Thank you

Hi,
1/ Has anyone done this? What did you use BAPI or ALE? ->USE ALE.
2>When a Customer Master IDOC is sent to SAP, if successful, a return code is sent back by SAP. This indicates that SAP has received the IDOC successfully. However, our requirement is that we have to know whether the IDOC was successfully posted within SAP. I am of the opinion that this is manual task within SAP and it should not be the function of the middleware layer as its responsibility is only to successfully deliver the IDOC's. I would welcome opinions on this issue. Please let me know If there is a way to determine if the IDOC has been successfully posted in SAP.
Yes u can view the idoc in WE02/WE05 (Idoc monitoring)
3>3/ Is there anywhere where I can get an XML representation of the Customer Master Record. I want to see the structure and the available fields. How can I get this info from SAP?
When u ase IDOC for customer , the basic type is DEBMAS05..Goto WE60, specify the basic type as DEBMAS05(latest) and then u have the all the segments , fields used with doucmentation.
Regards,
Nagaraj

Similar Messages

Update marketing attribute and customer master data via Survey Response

Hi,
I am creating a marketing survey. I have come to a point where I am able to get the reponses posted by the business partners.
Now I would like to update the BP's directly when they respond. The challenge here is I want to update both Marketing attribute and Customer master.
Is this possible with standard function modules. I am using version 4.0. Please let me know.
Regards,
Hemanth

Hello Hemanth,
Check my last response in the below thread, it could be a reason.
update marketing attributes in BP via survey
Thanks
Raja Pamireddy
CRM Marketing Forum Moderator.

Error while creating vendor master data via ALE

Dear All
I am trying to create vendor master data via ALE.
I am using message type CREMAS.
I get following error message in inbound system
No batch input data for screen SAPMF02K 0610
Message no. 00344
If i try to manually create vendor , there is no error. This particular screen belong to withholding tax, however all customizing settings for withholding tax are okay.
please help.
Thanks
Sanjeev

Try SAP Note # 96312 if that helps.

I am unable to upload the customer master data using BAPI.?

Hi Guru's,
i am unable to upload the customer master data using BAPI.(BAPI_CUSTOMER_CREATEFROMDATA1)
Please guide me how upload the data...
Thanks in iadvance
Srinivas...

Hello Srinivas
This BAPI does not allow to create a new customer from scratch but only to copy an existing customer to a new one and change its address data.
The reference customer has to be provided using IMPORTING parameter PI_COPYREFERENCE. See also the BAPI documentation for more details.
The BAPI does the same like transaction XD01 with Reference.
Regards
Uwe

BAPI CUSTOMER MASTER DATA

Hi
I want to create Customer Master data using BAPI
Can someone tell me what is step by step procedure for this.or just an example code.
Thanks
Namrata.

hi
use the BAPI BAPI_CUSTOMER_CREATE.
Go thru the documentation of this BAPI for more details..
Cheers,
Abdul Hakim
Mark all useful answers...

Query in customer master data upload ....?

Hi Guru's,
I am uploading the customer master data from presentaion server to customer tables using functional module SD_CUSTOMER_MAINTAIN_ALL.
while check the Function module separatly and it working properley and i am able to ctere customer...
and i am using the same function module in the program i am unable to upload ..could please check and let me know where i am doing mistake in the below program logis..and values also moving properly before calling function module..while calling the functinal module the controle comming out of the loop and program went to dump i am able to see the message in dump as like this(it may helpfull for resolve):
Name of function module...............: "SD_CUSTOMER_MAINTAIN_ALL"
Name of formal parameter..............: "O_KNA1"
Technical type of actual parameter....: "C"
Technical length of actual parameter..: 20 bytes
Technical type of formal parameter....: "u"
Technical length of formal parameter..: 3634 bytes
Name of formal parameter at caller....: "O_KNA1"
*& Report ZERP_CUSTOMER_CREATE_UPLOAD
REPORT zerp_customer_create_upload.
PARAMETERS:p_files        TYPE string.
*DATA :xkunnr(10)      LIKE kna1-kunnr. "unique KUNNR
DATA: gs_i_kna1           TYPE kna1,
      gs_i_knb1             TYPE knb1,
      gs_i_knvv           TYPE knvv,
      gs_return           TYPE bapireturn1,
      gs_i_bapiaddr1      TYPE   bapiaddr1,
      gt_t_xknvi          TYPE STANDARD TABLE OF fknvi,
      gwa_t_xknvi         TYPE fknvi,
      gt_t_xknbk          TYPE STANDARD TABLE OF fknbk,
      gwa_t_xknbk         TYPE fknbk,
      gt_t_yknvp          TYPE STANDARD TABLE OF fknvp,
      gwa_t_xknvp         TYPE fknvp.
TYPES:BEGIN OF gty_itab1,
      abc(305),
      END OF gty_itab1.
DATA: gt_itab1 TYPE STANDARD TABLE OF gty_itab1,
      gwa_itab1 TYPE gty_itab1.
TYPES :BEGIN OF gty_itab2,
       ktokd(4),        "customer account grp      kna1
       kunnr(10),       "customer                  kna1
       name1(35),       "name1                     kna1
       sortl(10),       "sort filed                kna1
       stras(35),       "house number and adres    kna1
       pstlz(10),       "postal code               kna1
       ort01(35),       "city                      kna1
       land1(3),        "country                   kna1
       telf1(16),       "tele phone no             kna1
       telfx(31),       "fax num                   kna1
       kukla(2),        "cust classificaion        kna1
       bukrs(4),        "company code              knb1
       akont(10),       "reconcilation acct        knb1
       vkorg(4),        "sales org                 knvv
       vtweg(2),        "distr chan                knvv
       spart(2),        "division                  knvv
       zterm(4),        "terms of payment          knvv
       bzirk(6),        "sales district            knvv
       vkbur(4),        "sales office              knvv
       vkgrp(3),        "sales grp                 knvv
       kdgrp(2),        "cust grp                  knvv
       waers(5),        "currency                  knvv
       konda(2),        "price grp                 knvv
       kalks(1),        "pricing procedure assign knvv
       lprio(2),        "delivery plant            knvv
       vsbed(2),        "shipping conditions       knvv
       vwerk(4),        "delivering plant          knvv
       inco1(3),        "inco1                     knvv
       inco2(28),       "inco2                     knvv
       kkber(4),        "cred control area         knvv
       ktgrd(2),        "acc assgn grp             knvv
       taxkd(1),        "tax classification 4 cust knvi
       bankn(18),       "bank account number       knbk -
        xkunnr(10),
       END OF gty_itab2.
DATA: gt_itab2 TYPE STANDARD TABLE OF gty_itab2,
      gwa_itab2 TYPE gty_itab2.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename                = p_files
    filetype                = 'ASC'
TABLES
    data_tab                = gt_itab1
EXCEPTIONS
    file_open_error         = 1
    file_read_error         = 2
    no_batch                = 3
    gui_refuse_filetransfer = 4
    invalid_type            = 5
    no_authority            = 6
    unknown_error           = 7
    bad_data_format         = 8
    header_not_allowed      = 9
    separator_not_allowed   = 10
    header_too_long         = 11
    unknown_dp_error        = 12
    access_denied           = 13
    dp_out_of_memory        = 14
    disk_full               = 15
    dp_timeout              = 16
    OTHERS                  = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT gt_itab1 INTO gwa_itab1.
gwa_itab2 = gwa_itab1-abc(305).
APPEND gwa_itab2 TO gt_itab2.
ENDLOOP.
LOOP AT gt_itab2 INTO gwa_itab2.
SPLIT gwa_itab2 AT ',' INTO gwa_itab2-ktokd
                              gwa_itab2-kunnr
                              gwa_itab2-name1 gwa_itab2-sortl
                              gwa_itab2-stras gwa_itab2-pstlz
                              gwa_itab2-ort01 gwa_itab2-land1
                              gwa_itab2-telf1 gwa_itab2-telfx
                              gwa_itab2-kukla gwa_itab2-bukrs
                              gwa_itab2-akont gwa_itab2-vkorg
                              gwa_itab2-vtweg gwa_itab2-spart
                              gwa_itab2-zterm gwa_itab2-bzirk
                              gwa_itab2-vkbur gwa_itab2-vkgrp
                              gwa_itab2-kdgrp gwa_itab2-waers
                              gwa_itab2-konda gwa_itab2-kalks
                              gwa_itab2-lprio gwa_itab2-vsbed
                              gwa_itab2-vwerk gwa_itab2-inco1
                              gwa_itab2-inco2 gwa_itab2-kkber
                              gwa_itab2-ktgrd
                              gwa_itab2-taxkd
                              gwa_itab2-bankn.
*moving files values from ITAB2 work area to global structure related to FM.
gs_i_kna1-ktokd   = gwa_itab2-ktokd.
gs_i_kna1-kunnr   = gwa_itab2-kunnr.
gs_i_kna1-name1   = gwa_itab2-name1.
gs_i_kna1-sortl   = gwa_itab2-sortl.
gs_i_kna1-stras   = gwa_itab2-stras.
gs_i_kna1-pstlz   = gwa_itab2-pstlz.
gs_i_kna1-ort01   = gwa_itab2-ort01.
gs_i_kna1-regio   = gwa_itab2-land1.
gs_i_kna1-telf1   = gwa_itab2-telf1.
gs_i_kna1-telfx   = gwa_itab2-telfx.
gs_i_kna1-kukla   = gwa_itab2-kukla.
gs_i_knb1-bukrs   = gwa_itab2-bukrs.
gs_i_knb1-akont   = gwa_itab2-akont.
*I FOR GOT TO INCLUDE THE ZTERM VALUE IN EXCELL SHEET SO INCLUDED HARD CODE HERE
gs_i_knb1-zterm   = '0001'.
gs_i_knvv-vkorg   = gwa_itab2-vkorg.
gs_i_knvv-vtweg   = gwa_itab2-vtweg.
gs_i_knvv-spart   = gwa_itab2-spart.
gs_i_knvv-zterm   = gwa_itab2-zterm.
gs_i_knvv-bzirk   = gwa_itab2-bzirk.
gs_i_knvv-vkbur   = gwa_itab2-vkbur.
gs_i_knvv-vkgrp   = gwa_itab2-vkgrp.
gs_i_knvv-kdgrp   = gwa_itab2-kdgrp.
gs_i_knvv-waers   = gwa_itab2-waers.
gs_i_knvv-konda   = gwa_itab2-konda.
gs_i_knvv-kalks   = gwa_itab2-kalks.
gs_i_knvv-lprio   = '02'.             "gwa_itab2-lprio.
gs_i_knvv-vsbed   = gwa_itab2-vsbed.
gs_i_knvv-vwerk   = gwa_itab2-vwerk.
gs_i_knvv-inco1   = gwa_itab2-inco1.
gs_i_knvv-inco2   = gwa_itab2-inco2.
gs_i_knvv-kkber   = gwa_itab2-kkber.
gs_i_knvv-ktgrd   = gwa_itab2-ktgrd.
gwa_t_xknvi-tatyp = 'UTXJ'.          "HARD CODE
gwa_t_xknvi-aland = 'US'.            "HARD CODED
gwa_t_xknvi-kz     = '0'.             "HADR CODE
gwa_t_xknvi-taxkd = '0'.             "gwa_itab2-taxkd.
APPEND gwa_t_xknvi TO gt_t_xknvi.
gwa_t_xknbk-bankn = gwa_itab2-bankn.
APPEND gwa_t_xknbk TO gt_t_xknbk.
gs_i_knb1-lockb          = 'X'.
gs_i_knvv-kzazu          = 'X'.
gs_i_knvv-kztlf          = 'X'.
gs_i_knvv-perfk          = 'X'.
gs_i_knvv-prfre          = 'X'.
gs_i_kna1-spras          = 'EN'.
CALL FUNCTION 'SD_CUSTOMER_MAINTAIN_ALL'
   EXPORTING
     i_kna1                              = gs_i_kna1
     i_knb1                              = gs_i_knb1
     i_knvv                              = gs_i_knvv
I_BAPIADDR1                         =
I_BAPIADDR2                         =
I_MAINTAIN_ADDRESS_BY_KNA1          = ' '
I_KNB1_REFERENCE                    = ' '
I_FORCE_EXTERNAL_NUMBER_RANGE       = ' '
I_NO_BANK_MASTER_UPDATE             = ' '
I_CUSTOMER_IS_CONSUMER              = ' '
I_RAISE_NO_BTE                      = ' '
PI_POSTFLAG                         = ' '
PI_CAM_CHANGED                      = ' '
PI_ADD_ON_DATA                      =
I_FROM_CUSTOMERMASTER               = ' '
IMPORTING
e_kunnr                             = xkunnr
o_kna1                              = xkunnr
E_SD_CUST_1321_DONE                 =
   TABLES
T_XKNAS                             =
     t_xknbk                             = gt_t_xknbk
T_XKNB5                             =
T_XKNEX                             =
T_XKNVA                             =
T_XKNVD                             =
     t_xknvi                             = gt_t_xknvi
T_XKNVK                             =
T_XKNVL                             =
T_XKNVP                             =
T_XKNZA                             =
T_YKNAS                             =
T_YKNBK                             =
T_YKNB5                             =
T_YKNEX                             =
T_YKNVA                             =
T_YKNVD                             =
T_YKNVI                             =
T_YKNVK                             =
T_YKNVL                             =
   t_yknvp                             = gt_t_yknvp
T_YKNZA                             =
T_UPD_TXT                           =
   EXCEPTIONS
     client_error                        = 1
     kna1_incomplete                     = 2
     knb1_incomplete                     = 3
     knb5_incomplete                     = 4
     knvv_incomplete                     = 5
     kunnr_not_unique                    = 6
     sales_area_not_unique               = 7
     sales_area_not_valid                = 8
     insert_update_conflict              = 9
     number_assignment_error             = 10
     number_not_in_range                 = 11
     number_range_not_extern             = 12
     number_range_not_intern             = 13
     account_group_not_valid             = 14
     parnr_invalid                       = 15
     bank_address_invalid                = 16
     tax_data_not_valid                  = 17
     no_authority                        = 18
     company_code_not_unique             = 19
     dunning_data_not_valid              = 20
     knb1_reference_invalid              = 21
     cam_error                           = 22
     OTHERS                              = 23.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
IF sy-subrc EQ 0.
    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    WRITE: / 'Error Message:', 'error in creation'.
ELSE.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'costomer', gwa_itab2-kunnr, 'created'.
ENDIF.
ENDLOOP.

please let me know if my qestion is not clear...
and please cinfirm me ..that can i use the function module (SD_CUSTOMER_MAINTAIN_ALL) instead of BAPI (BAPI_CUSTOMER_CREATEFROMDATA1) for uploading customer master data.
please respond me ASAP.
thanks in advance and will give full points
thanks&regards
Srinivas.

XD01 assertion failed error while updating customer master data

Hi Guys,
This is an error when I use transaction XD01 to create customers accounts, If you have any ideas do let me and we'll try it....
The error does not let an BDC or LSMW progress as well. There are also no recent sap notes on the same.
The error is as follow
ASSERTION_FAILED
Short text
The ASSERT condition was violated.
What happened?
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
I have a company code CG01 with sales organization CTS0 and I want to transfer or extend all the customer master data to another company code CG03 with the sales organization CTS0
The things that I have tried and not work
using xd01, fd15, fd16, fd01, does not wok and gives the error as above
The things that I have tried and it works
Change the sales organization from CTS0 to CTS1 I am able to post the customer master data, using any of the above tcodes and it does not give any error, however the client wants to sales organization to remain CTS0
So please give me any ideas as per your experience as this transfer of master data has to happen by Monday, else I'll be fried by my boss
My number is 9820029197
Will also keep you'll posted on any developments on this case,
Ronan Pinto

>
> Firstly I am from SAP FI, so totally new to SAP SD
>
Then you are best person to explain the reason on why the same sales organization, can't be assigned to different company codes. When a sales is done through one sales organization, then will the profit/loss be accounted in different company codes. Is it legally allowed in the country, where your customer is doing business? How you are going to develop the balance sheet? Again being the FI person, you are best judge to provide the details to your customer and not a SD guy.
>
> 1) How did the system not give an error while putting the data inside CG02 with sales organisaton same as CST0 same as in company code CG01.
>
I dont see any other method than removing the assignments in the backend and uploading the data. You can consult a Basis person to find the change logs for the assignment table. In my opinion, removing the sales organization from a company code assignment just for loading a customer master data and then reassigning to original sales org is a crooked method and/or not a professional method.
>
> 2) Since I have limited experience of SD, If I have to convince my client about the use of CTS1 sales organisation or a unique sales organisation against his argument that it worked for company code CG02, how should I do it.......
>
As explained above, how the sales will be accounted in different company codes (even if the system allows to assign the same sales org to different company codes)?
I would recommend you to post this question in FI forum (after closing here) to check what are the legal implications for this scenario.
Regards,

Impacts in COPA of changing material and customer master data

Dear experts,
In my company we are considering following scenario:
Currently mySAPerp 6.0 is implemented for all modules for the mother company.
We have developed a new global template where there are significant changes versus the existing system, especially in the SD processes. Material and customer master also change significantly in terms of content in the tables/fields and/or values in the fields.
The idea was to build the template from scratch in a new machine and roll-out all group affiliates, but now we are considering the possibility of making an evolutionary of the current system and try to stretch it to the processes defined in the global template.
The scenario we want to analyze is: Keeping same organizational structure in terms of Company code, CO area and Operating Concern in existing SAP client and make an evolutionary of the existing settings to the global template processes.
The doubts we are having are the following:
Changing material & customer master data: Impact in COPA
Option 1: Material master data and customer master data codes are maintained but content in the tables/fields is changed substantially, both in terms of logical content of specific fields and/or the values in the specific fields. We have following examples of changes.
Case 1: source field in material master changes logical content. E.g. Material master field MVGR1 is currently used for product series (design line) and the content changes to be the Market Segment. The product series will be moved to a classification field. At least 5 other fields are affected by this. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 2: the source field is not changed so that the logical content of the field remains but the values change, i.e. for the same concept there will be different codifications. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Case 3: Characteristics where currently the source material master field is a Z field and the derivation is via table look up and where the Z field changes to a classification field. How can you convert the existing COPA line items to ensure that attributes are aligned? Should new characteristics be created or just change the derivation logic of the characteristic?
Option 2: Material master data and customer data codes are re-created (codification of records is changed), meaning that new material and customer codes will exist and content in tables/fields is changed (as in option 1)
Case: material and customer codes are changed. How can data in terms of COPA line items be converted so that they are aligned at time of reporting?
Iu2019ve never phased a similar scenario and I fear that maintaining operating concern while changing source master data and also SD flows (we have new billing types, item categories, sales doc. Types, order reasons) may lead to inconsistencies and problems in COPA.
I would like to ask you experts if you have come across a similar scenario and if from your experience, it is something feasible to do or there are many risks involved. What can be the impact of this scenario in existing Operating Concern for both option 1 and 2 and what would be the key activities to perform to adapt the existing operating concern. What will be the impact of the needed conversions on P&L reporting?
Sorry for the long story. I hope you can help me out.
Thanks and Regards,
Eric

Hi,
First i think you will need to test if it works for new COPA documents created via billing.
If it works fine then the issue is if you wish to apply these changes to the historical data already posted.
Normally there are transactions like KE4S where you can repost the billing document to COPA
However this may not be viable for bulk postings
You can perform realignment (KEND) but this only works at the PA segment level (table CE4XXXX)
regards
Waman

What is the difference of customer master data between CRM and ECC

Dear all,
We are helping customer to evaluate using CRM or ECC to manage there customer master data, focusing on the benefit of using CRM system.
Can any one help to compare the difference between these two system?
some tips in my mind are:
1. CRM has a friendly user interface for user to adjust the layout, hide/display favourite information according to actuall req.
2. In CRM, user can change the field/assignment block description easilly
3. in CRM7.0, user can add new customzing field easilly via AET
4. CRM has a good any analysis platform to provide pie chart analytic
5. CRM store more customer infor. than ECC, such as Marketing attribute, account classfication...anything else?
any other benefit to use CRM for customer master data? Pls help!!!
Thanks very much!!
BR,
Hedy

I would agree with most of the topics you mentioned. Just one remark to topic number 5. Business partner doesn't have more data than erp. It has some more marketing oriented data, but on other hand doesn't have all finincial and credit data that are relevant for erp financial transactions.
In our company we have the following scenario: all business partners are created in crm (because there the sales activities are started and because we don' clasify at the begining all partners as customers but as prospects. and of course it has nicer user interface). but when we are closing the deals (ordreds are transfered to erp), we fill some additional (financial) data of that partner on erp side and clasify partners as customers.
Regards.

Unable to extract Customer Master data from MDC

Hello,
We creating an MDM-XI-ERP2005 Customer scenario. We want to work with all bussiness scenarios (not customizing scenario).
First I'm trying to extract Customer Master Data from EP 2005 using MDM_CLNT_EXTR.
I have created a New Variant which properties are:
Variant: CUSTOMER_TOTAL
Description: Send all customer data to MDM
Extraction Object: CUSTOMER_EXTRACT.
Target System: PI7.
But, the display jobs shows the following error: Could not determine recipients for message type MDMRECEIPT. Job cancelled after system exception.
We need to focus the problem. We have done the following ALE configuration.
SALE transaction:
In Basic Settings -> Logical Systems -> Define Logical System we have add the following logical systems:
              EUS100
              MDM: Master Data Management
              PI7: Process Integration 7.0
WE21:
Transactional RFC -> PI7, IDOC record types SAP Release 4.x
RFC destination: SAPSLDAPI
BD64
New Model -> PFMC
Add message type: Model iview: PFMC
                             Sender: EUS100
                              Receiver: PI7
                             Message Type: DEBMDM
WE20 transaction shows:
Partner profiles -> Partner Type LS (logical system)
                    PI7: Outbound parmtrs. DEBMDM, SYNCH.
Any idea will be very helpful,
Thanks in advance
Marta.
Edited by: Marta Sánchez on Jul 9, 2008 12:34 PM

Sorry because I made a mistake in my previous message. ALE seems to be correctly configured. I'll try to update correctly my current situation:
In WE02 I can see al IDOCs that I'm trying to send to XI. All them have the IDoc Status = 3 (Data Passed to Port OK) instead of 12 Status Dispatch OK :(. So, It seems an tRFC error.
SM58 shows me more trails: "Basic type 'DEBMDM06' is unknown"
before that I have done the following steps at SAP ERP:
    1. WE21: I have created a PI7 port with 700PI70CLNT RFC.
    2. SM59: I have checked successfully 700PI70CLNT RFC connection.
    3. WE20: I have created a PI7 Partner Type LS with the following inbound and outbound parameters: DEBMDM and MDMRECEIPT.
    4. BD64: I have created a Distribution Model with DEBMDM and MDMRECEIPT message types.
and at SAP PI:
     5.IDX: Port: SAPEUS. Client: 111. RFC Destination: PI7.
     6. technical and business system for sender SAP system(System Landscape Directory)...
- Maybe some of the previous steps is not correct....
- Is RFC Destination = PI7 is correct in step #5?
- Is also necessary to configure more steps in PI system like RFC destinations or Transactional port?
- I have read that is neccessary to check that the option "transfer idoc immediately" in we20. How?
Please any idea will be very helpful.......
Thank you!
Best regards,
Marta.

Delete Customer Master Data OBR2

Hi
I'm using LSMW to import data. I would like to delete it afterwards. Transaction OBR2 which is in spro Financial Accounting (New) -> Accounts Receivable And Payable -> Customer Accounts -> Master Data -> Delete Customer master data.
But it does not delete the sales are segment, it also does not allow me to delete general data if sales segment exists.
Can anyone please let me know if there is another way around this? Any other way to delete this test data???
Thanks in advance

Hi
Please go through the SAP documentation on how to perform deletion of customer master data.
This may help you in executing the function correctly.
<b>Delete Customer Master Data</b>
In this activity, you delete the master records for customers by using a program. Only use this program in the test phase.
Note
The company code for which master records are to be deleted, may not yet be flagged as productive.
Only master records for accounts which do not have any transaction data may be deleted.
Requirements
The general customer master data is only deleted for customers who are not also created as customers in Sales and Distribution.
Activities
Delete the master records for the required company codes.
Additional information
Refer to the SAPF019 program documentation for further information on the program.
Deleting Master Data
Description
This program deletes master data in Financial Accounting and is designed for preparing the system for productive startup. It deletes:
     Customer master data
     Vendor master data
     G/L account master data
You can run this program in three different ways:
1. Deleting general master data (in G/L accounts in one chart of accounts)
2. Deleting master data dependent on company code
3. Deleting general master data and master data dependent on company code
For each deletion run, you can specify whether or not the system should take into account the deletion flag in master records ("Delete per deletion flag only"). If it takes into account deletion flags, it uses the following standard logic:
Option 1: The "All areas" deletion flag must be set.
Option 2: The "Specified co. code" deletion flag must be set.
Option 3: It is sufficient to have the "All areas" deletion flag set.
Note: Deletion blocks are always checked at general data and company code-dependent data level. If there is a block at company code-dependent data level, then the general data is not deleted either. The deletion block takes precedence over the deletion flag.
General master data in Financial Accounting can also be used in other SAP applications:
     Customer master data in Sales and Distribution
     Vendor master data in Purchasing
     G/L accounts as primary cost elements in Cost Accounting
The program deletes the following:
     Change documents for master data
     SAPscript text files
     The following data is deleted for customers:
o     General master data
o     Bank details
o     VAT registration numbers
o     Addresses
o     Classifications
o     Credit management: across control areas
o     Credit management: centrally
o     Unloading points
o     Tax indicators
o     Contact persons
o     Licenses
o     Partner function limit
o     Shipping data
o     Master data in the company code
o     Dunning data
o     Linked data
     The following data is deleted for vendors:
o     General master data
o     Bank details
o     Contact persons
o     VAT registration numbers
o     Addresses
o     Classifications
o     Master data in the company code
o     Dunning data
o     Linked data
     The following data is deleted for G/L accounts:
o     General master data in the chart of accounts
o     Names in the chart of accounts
o     Key word list in the chart of accounts
o     Master data in the company code
o     Sample accounts, if selected
For customer and vendor contact persons, the addresses are not determined from central address management until the actual runtime. Therefore differences can arise as to the number of addresses in the detail log between the test run and the update run.
Automatic worklists for customers and vendors are also deleted with the general master data. Matchcodes are always deleted.
You may have to fix the number ranges after the program run.
The system makes changes to the database in the update run only. It will then also write a system log entry for documentation.
Requirements
General master data can only be deleted if no other application makes reference to the account. Use the resetting programs from
     Sales and Distribution (customer master data)
     Purchasing (vendor master data)
     Cost Accounting (G/L account master data)
If you want to delete only general master data, master data dependent on company code cannot have been created in Financial Accounting.
If you want to delete master data in a test company code, master data dependent on company code cannot have been created in any other company code except the test company code. The productive indicator cannot be set for the company code.
If a customer or vendor is referenced by another customer or vendor (for example, via fiscal address or alternative payee), you can only delete the referenced master record by deleting the referencing master record at the same time.
Furthermore, you can only delete master data in Financial Accounting if no transactions have been posted to the corresponding accounts. If there are transaction figures in one of the selected accounts, you have to manually access and run program SAPF020 (reset transaction data from a company code) before you can delete that account.
Output
The log lists every table which is processed in the program selection.
You can also create a detail log for each account type to find out why certain data cannot be deleted. The detail logs show you what other company codes and applications use the data and how customers and vendors are linked to one another.
Note
Since deleting or displaying even smaller volumes of data can result in runtime problems, you should run this program as a background job. Currently, the program individually deletes matchcodes for each master record in the database. Several match code IDs refer to each matchcode. This can place a considerable load on the database.
You cannot delete transaction data in individual accounts.
Important: The archiving programs in Financial Accounting are designed for the productive system.
If you are running this deletion program for the first time, then you must start program SAPF047 before deletion in order to generate link information.
I hope this may be of help to you
Good Luck
Hari

Outbond interface programme to upload customer master data.

Hi experts,
i need to develop an outbound interface programme to upload customer
master data,which will be received from sap and posted to web methods using
standard function mudule.can any one help me?

Hi,
Hi,
Primary you should have Message type, Idoc type and Function module or Report to process Outbound interface.
If your's is an Customized Process, then follow this.
1. Create Message type in we81.
2. Create segments in We31
3. Create Idoc Type in WE30.
4. Assign Message type to idoc type in WE82.
5.Create an Partner profile in WE20.
6.If you are creating an function Module create it in SE37.
7. Assign it to process code in WE41.
8. Charactersitics of FM in BD51.
9. Assign FM and IDoc And Message type in WE57.
<b>ALE IDOC</b>
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards

Customer Master Data interface to external using Seeburger on MDMP

Hi Experts,
   Currently, customer master data is interfaced to external system via IDOC. The middleware used is Seeburger.
   If the system is changed to MDMP, would there be any impact to this interface?
   Is Seeburger communicates in Unicode? If so, when the data is translated to Unicode when the data from R/3 is non-unicode?
   Thank you.
Regards,
Bing Fatt

Thanks Uwe,
I tried to create IDoc with BD10 for material master and I am getting two error msg as below.
Msg one
1 master IDocs set up for message type MATMAS
then Msg two
0 communication IDoc(s) generated for message type MATMAS
Is it able to get why this msg is comng and no IDoc's were generated..
Regards,
Senthil

Customer master data, Materials master data integration Integration in XI

Dear Experts,
I need your help in the following cases
We are integrating MDM 5.5 to ECC6.0 via XI 3.0.
1. I am not able to understand exactly what interfaces, mappings, integration scenarios from sap delivered MDM Business Content need to use for integrating customer master data , Materials from MDM 5.5 to ECC 6, As we are using standard content.
2. What idoc types needs to be created in ECC for these two scenarios ( customer, material /products).
3. Is there any way to see the field mappings easily in XI , as the MDM standard business content for XI used xslt mapping programs .
Could you please give helping hand with step by step procedure for customer, material integration in XI.
Help is rewarded and greatly appreciated.
Best Regards.
nag.

Hello Nag,
1. I am not able to understand exactly what interfaces, mappings, integration scenarios from sap delivered MDM Business Content need to use for integrating customer master data , Materials from MDM 5.5 to ECC 6, As we are using standard content.
If you import Business Content of MDM 5.5. You should easily figure out that by looking at the Message Mapping for DEBMAS03 IDoc.
.2. What idoc types needs to be created in ECC for these two scenarios ( customer, material /products).
No need to create any Master IDocs in SAP system. You can find them with the name DEBMAS (For Customer) and MATMAS (Material).
3. Is there any way to see the field mappings easily in XI , as the MDM standard business content for XI used xslt mapping programs .
If you really want to know how the XSL Mapping is programmed. You can export the XSL from XI and open it in standard XML /XSL editor (say Stylus Studio ) to see how the output is programmed
Regards,
Ashwin M
Dont forget to mark helpful answers

Move Customer master data to btween systems

Hi Gurus,
I m facing a question to move customer master data between systems. how can we do it other than writing bdc programs.
any responses would be awarded,
thanks a lot.
samson

Hi,
You can use ALE distribution model (BD64) and then send the data using BD12/13 transactions.
Regards,
Eli

Customer Master Data via a Bapi/ALE

Similar Messages

Maybe you are looking for