Partner status in ALE
Hello all,
I need to set the partner status from I(inactive) to A. But the field in disabled and also menu Partners-Change doesn't work(inactive). Is it about missing rights or do I something wrong? How to change the status?
Thanks a lot.
Hi Smriti,
Regarding working on the faulty IDOC
In WE19 check what Function module will be used to post the data, you can see it when you go to 'standard inbound'. Then you can debug it when you click to the button 'inbound function module', here enter the function module and click 'call in debugging mode' and 'in foreground', then press the button 'enter'. Now you are in the debugger and can check why the error occurs and what should be filled.
If you know the error number set watchpoint at sy-msgno = *** or just set breakpoint at statement message.
If this is only happening for one confirmation, the standard approach to delete this is the following.
Issue:
The corresponding IDOC for the confirmation document has not been processed successfully and ended with error in the backend.
Solution:
Because of this there is entry left in the table bbp_document_tab,
which is not allowing to cancell the confirmation document.
Please find the attached note 338985, which contains the procedure to
to delete entries from table bbp_document_tab.
Hope this helps,
Kind Regards,
Matthew
Similar Messages
-
Generation Partner Profiles from ALE Distribution Model
Hi ABAP/EDI experts,
I am a trainee. I am getting training from Pvt consultancy. I am working on SAP Demo systems.
I am trying t generate an IDoc using ALE method.
IN SALE window, I created two logical systems,ZVK_SS_800 and ZVK_SS_820. I assigned them to two clients 800 and 820 respectively.
In SM59 i created an RFC connection ZVK_RFC004 of type 3. Here I gave the client Number as 820. ( I'm not sure what to give)
In BD64, I created an ALE Model and added the message type MATMAS with Sending and Receiving Logical systems.
From the Environment drop down menu , selected generate partner profiles and executed with defaults checked. ( Transfer IDocs Immediatley and Trigger Immediately).
I got the following log.
Log For Partner Profile Generation:
Partner:
In Green Color
Partner ZVK_SS_800 as partner has been Created ( Sending System)
Partner ZVK_SS_820 as partner has been Created (Receiving System)
Port:
In Red Color
Port Cloud not be Created
RFC destination ZVK_SS_820 not specified for system ZVK_SS_820
Enter the RFC destination and Restart the generation.
Please help me to fix this probelm.
Any kind of Help will be surely rewarded.
Thanks,From SM59, you can Test your RFC Connections between Clients. I would do this from Client 800 and test the Connection to Client 820. If that checks okay, I would then try SM59 on Client 820. Check the RFC Connection from Client 820 to Client 800. Be sure you have your Logical Systems defined on Both Clients. You can also double click on your Error Message to see if there is a Long Text Available that might give you further information as what needs to be corrected. I am not an Expert in this area, but have setup several ALE Models for my Variant Configuration without any problems. If you could include your EMail Address on your Business Card I could EMail you my instructions. Your Basis person may also be able to help you based upon your Error Message.
-
PO vendor partner role through ALE/IDOCs
We have ALE/IDOC interface with vendor. The requirement is PO will be sent to the ordering vendor and invoice should be received with PI vendor. We are using stardard message types for purchase order (outbound) and INVOIC (inbound).
Could you please guide me on how to set up partner profile in WE20? Do I need to define both the vendors as partner? and what partner function should I select in inbound and outbound for both the vendor? Any other settings is required?
Thanks in Advance
SagarHi,
The earlier answer was to your this question
Could you please guide me on how to set up partner profile in WE20?
Now to set up the partner function follow as below
In Spro>Purchasing>partner determination >first define the partner roles , role VN for vendor,role PI for invoicing party and OA ordering address are standard available then
Define permissible roles per Vendor A/C group ..based on account group of vendor you need to define a perticular partner role is permitted
Go to define partner schmeas for vendor master >select L1 vendor>partner functions in procedure>here you check your roles are available there 2 check boxes if you wnat a perticular role mandatory in vendor master you can check mandatory and if you want an option of changing the partner you can make it changable , better to make these two roles mandatory and OA changable
Go to assign partner schemas for vendor master assign L1 for your vendor a/c group
Then go to partner settings in purchasing document define partner schema select std.po >function in procedure>check roles VN,PI,OA
Select no change mandatory and higher level for all three
Go to assign schemas for docuemt>assign 0002 for document type in question
Thanks
Diwakar
Edited by: diwakarnd deshpande on May 13, 2011 8:24 PM -
Confusion on partner function of ALE process
Hi experts,
Now I am developing the ALE for message type ORDERS in inbounding process for testing purpose. Our customer is running their business in SAP and her company code is 6000 in her SAP system, and our company is vendor in her system, the vendor number is 1100. She create a purchase order and run the transaction code ME9F then the IDOC will send to our SAP system, and then the sales order is created in our system. Actually the whole process is OK. But I am really confused by the partner function setting and sales area setting in VOE4 and VOE2.
In VOE4, the setting is below:
Customer Ext.Function Name Exnternal partner Int.no
6000 SP Sold-to party 6000 6000
6000 BP Bill-to party 6000 6000
6000 PY Payer 6000 6000
6000 SP Ship-to Party 6000 6000
In VOE2, the setting just like below:
Customer Vendor number Sorg. Dchl Dv Saty
6000 0000001100 1000 12 00 OR
We had to create a customer number 6000 in order to make the ALE process smoothly. So I just want to know:
1) We really need to make our customer number same as company code of customer in her SAP system if we use ALE ??
2) If answer of 1) is yes, then in our production system, the customer numbers are different from their company codes, what and how do you suggest to mapping the is relationship?? Use a user-exit in IDOC??
3) if answer of 1) is no, how can we make the ALE go next smothly??
Can any one give me a suggestion on above??? Thanks in advance.
Joe
Edited by: Joe.GR Chen on Jun 19, 2009 11:23 AMhi,
to add partner function sales employee follow these steps:
1. img>S & D>basic functions>go to partner determination screen and select customer master and select your partner proceedure.
2. now double click on partners in partner proceedure and add partner function SE using new entries and save.
3. now assign the partner function to you account group and save
to create a sales employee goto t code PAL1 and create sales representative.
to add sales rep to your customer master goto your customer master using XD02 and in sales area tab goto partner tab and add the partner function SE and the sales rep number and save
regards,
krishna prasad -
Dear experts
Can anyone recommend a way to default a status profile and status on to a partner at time of creation?
It has to work when you create a partner just by running BD, also when partner was created on R3 and comes to CRM on a bdoc.
I have tried to do this with BAdI PARTNER_UPDATE, method CHANGE_BEFORE_UPDATE where I have some code that ends by calling function BUPA_STATUS_ADABT_BSVA, but although this usually works ok, sometimes it terminates with SQL_DUPLICATE_INSERT (e.g., processing a bdoc with multiple partners in it) so it is not reliable
Any ideas much appreciated
Thanks, BenNo fault - duplicate errors caused by duplicate implementation of the code in 2 badis!
-
Regarding ports and partner profiles in ALE.
Hi All,
Please tell me how to transport the partner profiles and ports from Development to Quality systems.
Please reply asap.SALE Area Menu for ALE configurations.It includes transactions for
Logical System definition and linking it to a client, Transactions for
RFC Destination and Port Definition Etc.
SM59 RFC Destination
Here we specify the login settings for the destination including
the I.P address or Application Server name and the User name and
password.The information entered here is used to run Remote Function
Calls(RFC ) on the destination server .We can create number of types
of RFC Destinations but 3 types are important .
R/3 (R/3 to R/3), LS(logical system) and TCP/IP.
The name of the RFC destination should be same as that of Logical
System as it helps in creation of automatic partner profiles.
WE21 Port Definition.
There are 6 types of ports but only 2 types File and Transactional RFC
types of ports are important.
We have to specify the RFC Destination before a port can be created.
WE20 Partner Profile
Here we create partner profile for each and every partner from / to which
the messages will be exchanged.There are 6 types of PF generally only
profiles of type LS(Logical System) ,KU(Customer) ,LI(Vendor) is used.
We specify the partner number and partner type and the agent and
the agent type responsible for handling of errors .
For every message send to the partner we have a outbound record and for
evry message coming from the partner we have the inbound record .
We specify the message in the otbound/inbound records ,double
clicking will take us to the detailed screen where the IDOC Type ,Port
and whether the IDCO will be immediatelt processed or collected are
mentioned.
Reward points if helpful.
Thanks
Naveen khan
Message was edited by:
Pattan Naveen -
hi sir/medam
i m tring to learn ale...
what perpose of partner port...and how creat partner port? plz tell in detail
thanksHi Mukesh ,
Partner Profile is define the way data transfer between two systems, it's contains both inbound and outbound parameters.
T -code for Partner profile is <b>WE20</b>,
Before that we should create port for communication
Tcode for Port creation is <b>WE21</b>.
We can create partner profile automatically in <b>BD64</b>.
Regards,
Vijay -
Hi gurus, I need to extract to BW information about status - in tx bp it is located at folder Status, fields GV_SCHEME_TEXT and GS_USER_STATUS_TC-STAT_TEXT. Unfortunatelly it is lart of dtructure SAPLBUPA_DIALOG_JOEL. Can you help me fto find table(s), where is stored information regarding Business Partners and its status? Thank you a lot..
Hi,
Kindly check in the following tables:
1. CRM_JEST - Individual Object Status
2. CRM_JCDO - Change Documents for Status Object (Table JSTO)
From the above tables i think you can be able to extract status information of Business partner.
Hope this helps.
Venkat -
Business Partner Transfer using ALE/IDOCS
Dear Gurus,
I am using S.R.M. 5.0 system. I am encountering scenario of transferring the business partners from S.R.M sytem to C project which is again add-on module provided by SAP. I have created Distribution Model and have assigned the message type BUS1006 (message type for Business Partner). But I am not able to find the transaction to send the data across to CPD system like BD10 is for transferring material in R/3 system.I have also observerd that the dala eleement of the business partner has got change pointer attached to it. I have got two questions.
1. Is the method that I followed is correct to transfer data? I did it by seeing PPT .If yes than what is the t-code to transfer the business partner equivalent to BD10.
2. In case of change pointers begin activated how should I transfer data? if any documentation is there that will be helpful?
Thanks and Regards,
Saurabh Chhatre
Thanks and Regards,
Saurabh ChhatreHi Sergio,
When I tried BUPA_SEND , I came across another transaction BUPA_CALL_FU.
This transaction allows us to select function modules that needs to be called for sending the business partner from S.R.M 5.0.Have you got any idea which are the mandatory F.M's that needs to be selected. I am asking this because there are few F.M's which do not exist in the system.
Or have do you have any idea how we can create these F.M's. As these are standard I am thinking it must be done through customization.
Thanks in advance
Thanks and Regards,
Saurabh Chhatre -
Same message type in different partner profiles in ALE
Hi,
I have a situation where we need to send an IDoc of message type ORDERS to two partners of type 'LS'. Configured partner profiles in WE20 and added message type for both the partners. Also configured the condition records.Now the question is how the system will know for particular vendors a particular partner 'LS' should be chosen? In condition records we don't have option to configure a vendor for a particular logical system.
Please advice.
Regards,
KrishnaFor Vendors, why are you using LS, u need to use LI.
-
How is partner profile for ALE/IDOC transported?
Hi experts,
How is a request created for transporting configurations in ALE/idoc.
Valuable answers will be generously rewarded.
regards,
Shrita.Hi,
some configurations are client dependent and some are client independent.
so client dependent configurations are transported to different clients using SCC1 transaction.
and client independent configurations they refelect automatically.
Regards
vijay -
Hi,
Iam trying to send a MATMAS Idoc from one client to another client , which is in the same R/3. The outbound staus is 03 and the inbound is 51.
I just created a material (Material details are attached below for reference) and send tht material to the other client using BD10.
can you please tell me the Inbound function module name which i should use to post it again.
Material Name:KRMATERIAL
Industry sector : Mechanical Engineering
Material Type : Finished Products.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
Thanks
-KarthikHi Karthik,
Just follow the procedure, this is for MATMAS
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
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
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
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
<b>Reward Points if this helps,</b>
Satish -
ALE Partner type ( Parnter profiles)
Can I select vendor and customer as partner type while creating partner profile in ALE configuration.
If 'YES',please let me know, where to maintain the mapping between vendor(sending system part type)
and customer(receiving system partner type).
Thanks
N.Prasad BabuHi friends,
Thanks for ur prompt response.I have already created
partner profiles.Still I am getting errors in the receiving end.
In scenario is :
SENDING SYSTEM: 800(client)
Partner profile was created whose
Part.type: vendor
Port : trfc port which has rfc desination to client 110
RECEIVING SYSTEM: 110(client)
Partner profile was created whose
Part.type: customer
Port : trfc port which has rfc desination to client 800
Now,Do I need relate partnet type vendor to partner type customer. if "YES", how do i do it. -
ALE Transactional and VA01 Again
Dear Friends
Some of you gives me good links fordocumentation but after customizing and done a lot of thing I can't have an automatic IDOC when I create a sale order via VA01.
As it was explain in the documentation I have written a module function and done a lot of thing but nothing appens.
With an user exit SAPMVFZZ I can create the IDOC and it well sent to the good port. So BD64 is good.
==========================================================
<b>Table NAST is not filled up when I create an Sales order.</b>
==========================================================
Here after a resume of what I heve done.
If you have a good idea and may be you know why no IDOC when I create an Sales order, you are wellcome.
1. OUTBOUND PROCESSING
1.1. Create IDoc type (WE30) Client independent
IDoc type ZSALES01
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZSALES01 and click on Basic IDoc type, click the Create icon
EC1VBAK (father) and two sons
EC1VBAP Enter EC1VBA2
1.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> ALE Development -> IDoc -> IDoc types Development -> WE81 logical messages ZORDER01
Save and exit.
1.3. Link message to IDoc type (WE82 & BD69) Client independent
To link the message types to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> ALE Development -> IDoc -> IDoc types Development -> WE82 IDoc Type for message
Enter the message type ZORDER01 and the Basic IDoc type as ZSALES01
Save and exit the result is set in SAP table EDIMSG
1.4. Transaction NACE / NACT
Creation of OUTPUT TYPE Z001 for application V1.
Access sequence 004 = SalesOrg/Sales Order Type
<b>Default Value</b>
Dispatch time send immediately
Transmission Medium Distribution ALE
<b>Time</b>
Timing 2 is set off Job and time entry
Condition table 5 has been generated.
Consistency check for output control all is OK
Assignment output type to partner function In the IMG
Creation of Procedure Z00001 OUTPUT FOR IDOC ZSALES01 for Usage B and application V1
The control procedure: control type z001 requirement 2 (Order confirmation)
1.5. Assign Output type to partner function
Z001 A SP (sold to party)
Transaction V/43 assign Output determination Procedure
Allocate Sales Document header
Sale doc type OR Output procedure Z00001 Output type Z001
1.6. Transaction WE20
Partner profile
Partner number 0000000001
Partner type KU
Partner role SP
Message type ZORDER01
Partner status Actif
Output options
Port A000000002
Pack size 1
Transfer IDOC Immediate YES
Cancel processing after syntax error YES
IDOC Type Basic type ZSALES01
Message control
Application V1
Process code ZVA01
Message type z001
Result of checking (program RSECHK07) with partner 0000000001 and partner type KU: All OK
Table EDP13, table EDP12 message control are well filled up.
A module function is created with the good parameters ZSALESORDERIDOC
The process code point to a function ZSALESORDERIDOC (transaction WE41) Outbound process code
Process code ZVA01 Linked to module function ZSALESORDERIDOC processing with ALE service
Function module version 3.0
Table EDIMSG Output Types and Assignment to IDoc Types give
Message type ZORDER01 Basic type ZSALES01 release 50A
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Enter the message type ZORDER01 and the Basic IDoc type as ZSALES01
1.7. Maintain object type for message type (BD59) Client independent
Type in your message type ZORDER01 and press enter
Enter your object type, KUNNR (We need to use the customer as a filter object), the segment name where KUNNR resides, EC1VBAK, a number 1 for the sequence followed by the actual field name KUNNR
1.8. Configuring the Distribution Model BD64
This task is performed on your ALE reference client.
Manual Configuration (BD64) Client dependent
Create a new model. (Create model POCALE)
POC ALE to send Outbound Idoc POCALE
Choose the receiving systems to which the sending system must forward message type ZORDER01 to.
We have generated the model view after creation.He Ferry,
I try your checking and with VA02 -> Enter <sales order> -> Enter -> Extras -> Output -> Header -> Edit.
The system propose me Z001 when I click on OUTPUT TYPE (F4).
I have selected Z001 and submit. The following message comes "Processing program missing for output Z001 " ==> "No processing program is defined in table TNAPR for output type Z001 (transmission medium A) in application V1."
In transaction NACE for V1 and OUTPUT type, in TAB Processing routine I can add one program and Form routine.
The module function created zsalesorderidoc has generated a program (SE38) ZSALESORDERIDOC===============FT
Is this one I have to use or I have to create a special one? If I have to create one may I have a model?
In the program ZSALESORDERIDOC===============FT we have these FORM.
FORM EXISTENCE_CHECK CHANGING VARIA.
FORM FUNCTION_CALL.
FORM CLEAR_DATA.
FORM CLEAR_TABLE.
FORM DELETE_LINE USING KEY INDEX.
FORM INIT_EXCEPTIONS USING NAME.
FORM PARAM_ACCESS_TYPES USING KEY DEST P_MODE P_UPPER.
FORM PARAMETER_SET USING NAME DIRECTION VALUE.
PERFORM CB_CALLBACK_VALUE_SET(SAPLSEUJ)
USING VALUE
CHANGING %_IOBJECT.
FORM PARAMETER_GET USING NAME DIRECTION
CHANGING VALUE
OLD_VALUE.
FORM PARAMETER_TABLE_SET USING NAME VALUE.
FORM PARAMETER_TABLE_GET USING NAME
CHANGING VALUE.
FORM PARAMETER_DESCRIBE USING CBPROG
NAME.
FORM PARAMETER_CONTAINER TABLES LCONT STRUCTURE SWCONT
USING NAME
DIRECTION .
FORM TABLES_CONTAINER TABLES LCONT STRUCTURE SWCONT
USING NAME
DIRECTION.
FORM SET_VARIABLES USING KEY VALUE.
FORM GET_VARIABLES USING KEY
CHANGING VALUE.
FORM PARAMETER_READ_INPUT USING NAME
KEY
CHANGING VALUE.
FORM PARAMETER_READ_OUTPUT USING NAME
KEY
CHANGING VALUE.
FORM PARAMETER_COMPARE USING NAME
CHANGING VALUE.
FORM EXPORT_IMPORT_MEMORY USING SEL KEY STRUCTURE EXPORTKEY.
FORM EXPORT_IMPORT USING SEL KEY STRUCTURE D102N_EXPORTKEY.
FORM GET_EXCEPTION_DIFFERENCE
FORM COMPARE_DATA
TABLES DIFFERENCES STRUCTURE UNTERSCHIED
USING FIELD
CHANGING RETCODE.
Thank you for All
Best regards
Henri -
Hi friends need some help in ALE IDOC !
For training purpose I am trying to create an IDOC using ALE
where I am using the same client as server as well as receiver......So I am using as receiver "NONE" . this is already present in the SM59 under logical systems..
But i cant create a port for that...as its saying its not compatible with the TRFC "
Can any one tell me what is the way to create the port ?Hi,
You are new to ALE and IDOCs so I am giving all step by step to do the ALE.
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
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
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
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
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
Thanks
Sarada
Maybe you are looking for
-
every time i want to audio chat with a friend it starts connecting then i wait for about 30seconds then it says that it cant connect because the guy im talking with says that he acsepted my invite but ichat said he didnt please help
-
Gmail App Password - why can't I use it?
Hey guys. For extra security, I always use like to use the Google App Password option (instead of my main password) on mobile devices. https://security.google.com/settings/security/apppasswords (don't have 10 posts to post a link) Got a new Z30 today
-
ok so my hard disk recently became full unexpectedly so I downloaded a few applications to clear out the small unneeded files that just take up disk space. Upon clearing out the files, I think the program might have deleted some vital files because w
-
my ipod wont play music on my ihome and I know it is not the ihome because I put my brothers ipod on it and it worked I dont know what is going on please help me
-
NVRAM Password command broken?
Hi people, I have noticed a strange issue for about a month, most likely caused by the OS X 10.7.2 update: When you are using the Open Firmware Password tool you can set the bootup password to prevent the usage of bootup commands like CD booting, PRA