on 12-21-2007 6:31 AM
Hi ,
I am currently working for the Business Partner interfacing through ALE .
I am tring to get some data regarding business partner from IBM websphere , for that I need to work in the datasets of the BP for connecting with IBM websphere through ALE IDOC .
I need all the business partner message type released for this , so I asked my basis team to apply note 940415.
But its showing error
"SAP note 0000940415 cannot be implemented " when they have tried to apply it .
Can any one help me out about the problem ?
How can it be resolved ?
Its very urgent .
Regards
Debasri sarkar
sarkar.debasri@gamil.com
debasri_sarkar@satyam.com
Hi Debasri,
The note should have some release restrictions or patch level requirement.
Please check if the note is relevant to your system release.
Regards,
Siddhesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Debasri,
There is nothing to implement in this note, the note only states that:
SAP does not support ALE interfaces for the BAPIs of the business partner.
I have downloaded the note and copied the contents below: Please check the Reasons and Prerequisites section.
================================================
Symptom
The ALE interfaces for the BAPIs of business object type BUSISB990 BusinessPartnerFS 'Business Partner for Financial Services' are not released and not supported by SAP.
You want to change the business partner data in the system using ALE. For these purposes, message type BUPA_INBOUND_MAIN_SAVE_M is released with the processing module BUPA_INBOUND_MAIN_SAVE for business object type BUS1006 as of Release SAP_ABA 6.40. Using the complex interface of the business partner (BUPA_INBOUND_MAIN_SAVE), you can change individual datasets as if you were using the BAPIs. Furthermore, the complex interface of the business partner allows you to make the changes to the entire object.
Other terms
BAPI, BP_BAP, IDoc, release, complex interface
Reason and Prerequisites
SAP does not support ALE interfaces for the BAPIs of the business partner.
Solution
This note applies to the following ALE message types that are not supported:
BUPAFS_FS_CREATE_FRM_DATA
BUPAFS_FS_CREATE_FRM_DATA2
BUPA_C_ADDADDRESS
BUPA_C_ADDSTATUS
BUPA_C_BANKDETAIL_ADD
BUPA_C_BANKDETAIL_CH
BUPA_C_BANKDETAIL_REMOVE
BUPA_C_CHANGEADDRESS
BUPA_C_IDENTADD
BUPA_C_IDENT_REMOVE
BUPA_C_INDUSTRYSADD
BUPA_C_INDUSTRYS_REMOVE
BUPA_C_PASSWORD_CH
BUPA_C_PASSWORD_CR
BUPA_C_PASSWORD_DELETE
BUPA_C_PASSWORD_INIT
BUPA_C_REMOVEADDRESS
BUPA_C_ROLEADD
BUPA_C_STATUS_REMOVE
BUPA_C_TAXNUMBERADD
BUPA_C_TAXNUM_CHANGE
BUPA_C_TAXNUM_REMOVE
BUPA_FS_ADDADDITIONALDATA
BUPA_FS_ADDADDRESS
BUPA_FS_ADDADRESSUSAGE
BUPA_FS_ADDBANK
BUPA_FS_ADDCUSTOMFIELDS
BUPA_FS_ADDDIFFTYPE
BUPA_FS_ADDEMPLOYM
BUPA_FS_ADDEXTERNID
BUPA_FS_ADDFISCYEAR
BUPA_FS_ADDFISCYEAR2
BUPA_FS_ADDRATING
BUPA_FS_ADDREPORTING
BUPA_FS_ADDTREASURY
BUPA_FS_BANK_REMOVE
BUPA_FS_CHANGEADDITIONALDATA
BUPA_FS_CHANGEADRESSUSAGE
BUPA_FS_CHANGEBANK
BUPA_FS_CHANGECUSTOMFIELDS
BUPA_FS_CHANGEDIFFTYPE
BUPA_FS_CHANGEEMPLOYM
BUPA_FS_CHANGEFISCYEAR
BUPA_FS_CHANGEFISCYEAR2
BUPA_FS_CHANGERATING
BUPA_FS_CHANGEREPORTING
BUPA_FS_CHANGETREASURY
BUPA_FS_CHGADDRESS
BUPA_FS_REMADDRESS
BUPA_FS_REMOVEADDITIONALDATA
BUPA_FS_REMOVEADRESSUSAGE
BUPA_FS_REMOVECUSTOMFIELDS
BUPA_FS_REMOVEDIFFTYPE
BUPA_FS_REMOVEEMPLOYM
BUPA_FS_REMOVEEXTERNID
BUPA_FS_REMOVEFISCYEAR
BUPA_FS_REMOVEFISCYEAR2
BUPA_FS_REMOVERATING
BUPA_FS_REMOVEREPORTING
BUPA_FS_REMOVETREASURY
.
===================================================
This means there is nothing you can do here with this note.
Regards,
Siddhesh
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.