ALEREQ idoc type from PI system

Hi,
I have to change the vendor data from Inbound idoc which will be coming from PI system.
but, to get the inbound idoc for vendor we have idoc type as CREMAS05 and message type as CREFET
But,at PI side to send the vendor data, they see the idoc type as ALEREQ01 for message type as CREFET.
Kindly provide me the resolution.
Thanks in Advance.

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Similar Messages

Is it Possible to import an IDoc type from R/3 into APO system

Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roseline

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

How to check the Idocs sent from SAP system

How to check the outbound Idocs sent from SAP system to target systems.
How to know the message types and target systems.

Hi,
In Addition with the above mentioned transaction code(WE02), u can check out idocs in these table - EDIDC, EDID4, EDIDS. Depending on different status you can differentiate them as Inbound or Outbound Idocs...
Cheers...
Santosh.
Mark All Usefull Answers...

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

Creating IDoc Type from Change Pointers using RBDMIDOC

Hi All,
we are executing program RBDMIDOC(Creating IDoc Type from Change Pointers) evrey 15 minuts in background.
Issue : if some jobs are taking more than 15 minuts then next jobs are failed,
is next job will pick up any idocs that were missed?
there is no extesion's and ther is no Z-fields are used in that message type , we are used OILMAT as mesage type.
Regards,
DSK
Edited by: suresh dameruppula on Aug 5, 2008 2:04 PM

Hi,
Include a step in your job and have a program which checks if a job is already running. If yes do not start the next instance of the same job.
in the custom program just call function module
   CALL FUNCTION 'ZBC_JOB_ALREADY_RUNNING'
      EXPORTING
         JOBNAME           = p_job
      IMPORTING
         JOB_RUNNING       = w_count
      EXCEPTIONS
         JOB_NOT_SPECIFIED = 1
         OTHERS            = 2.
Code within FM ->
   select count(*)
   into   job_running
   from   tbtco
   where jobname = jobname
   and    status = 'R'.
where p_job is the job name.
w_count is current running job count. If its greater than 1, then stop the 2nd with an error message.
Rgds,
Hema

Outbound delivery creation with inbound IDOC transfer from Java system

Dear Experts,
       The scenario we are having is really very interesting. Hopefully its a good learning for me and also for others also.
The scenario is,
               After sales order creation the details will be sent to one Non SAP system (Java) for performing some tasks related to forwarding agent decision, shipping date and etc. Once the details are finalized in that Java system then, the details needs to be transferred to SAP as "Inbound IDOC" process. For this proposed to use the SAP Jco middle ware.
             Once the details transfered from Java system to SAP then, the outbound IDOC needs to get generated automatically. Assuming the stock for that sales order line item is available. Also one more complexity is, our client is using custom transaction (ZVl10C) for delivery creation.
Now Query is,
               1. Which IDOC, message type and Functional module needs to be used for creating the delivery automatically..??
               2. As per assumption, stock of that sales order line item should be available. Due to some business reason the stock was removed during inbound IDOC transfer then, what will happen to the IDOC..?. How to avoid this situation..??
               3. As we told we are re going to use SAP Jco b/w SAP & Java system. In this case, how the data will get transfered from Java system to SAP..?
Thanks in advance for the replies I am going to get
Regards,
VEL

Didn't get any feedback from experts for long time. So we are closing the question

Message type from Logical system

Dear All,
I need develop an inbound where the info is coming from HR system. I found Message Type HRMD_A can be utilized for the development, however im not so sure if the message type HRMD_A is originally exist in my R/3 4.7 or it was being distributed by the HR system previously via BD64.
Please comment on how can i check for it.
Below are the related info for Message type HRMD_A that i found in my R/3 4.7:
Message type - HRMD_A
Basic type - HRMD_A06 (for release 620)
Process code - HRMD
Inbound FM - IDOC_INPUT_HRMD
Thank you.

Hi Atish,
Thanks for your reply. Let me recap my scenario and please point me out if i'm wrong again.
For my case, Message type HRMD_A exist in both R/3 and HR system. Since it exist, then we do not need to distribute from HR again via BD64. Right?
IDOC can be passed from HR to R/3 without any additional config right? Assume partner profile and RFC destination has been configured correctly.
Please comment.

How to send delivery status by idoc format from EWM system?

Hi gurus,
You know we can send GR(posted) from EWM to R3 system, while in our scenario, we also need to send inbound delivery status( including posting, posted) from EWM to Non-SAP system via PI.
Can we implement that by idoc? Do we have to use PPF? How to develop in PPF to send message to PI?
Thanks in advance.

Hi kishore,
Thanks for your reply.
I tried to find how SPPFCADM send idoc in ther relevant method, but you know it's just some object oriented code which is not easy to understand and I couldn't find where send idoc and where can be enhanced.
I found that /SCWM/ERP_MAPOUT is the implementation name for the method of inbound delivery to ERP system, also there is an action "XI Message:lieferinfo:inbound delivery", can it be used to send idoc to PI/XI system?
Thanks.

Idocs missing from source system

Hello,
I am trying to extract data from R3 to BW. I am getting an error message in BI, No idocs arrived from the source system.
In SM58 system showing the message 'No service for system SAPECC, CLIENT 800 IN INTEGRATION DIRECTORY'. Please help on this issue
Regards,
Ramesh

Hi Ramesh,
Check whether the connection is proper between BW & R/3.
Goto your Source system> Right clcik> Check.
You can also check the following :
No Idocs arrived from the source system.
Idocs missing: No selection information arrived from the source system
Error when updating Idocs in Source System
Hope it helps!
Regards,
Pavan

No IDOCS arrived from Source system to BI for generic extraction

Hi All,
While loading data from r\3 generic data source to BI, I am facing the below problem.
1. Using Full Load:-
The request from r\3 to psa turns red after a while. The request monitor says:
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
Details Tab shows : request green
Under that Extraction tab shows red
missing messages.
Transfer (IDocs and TRFC): Errors occurred .
Request IDoc : Application document not posted
I ran Transaction BD87,BD73 and execute with proper selections.
Upon checking the idoc in source system Their status is 51 , which says
Diagnosis
The control parameters for communication with the BW server are not
complete. A BW PlugIn upgrade could be the cause of the problem.
System response
Procedure
Depending on the Release of the BW server, proceed as follows:
BW Server Release 1.2B: Source system: Update InfoSource metadata
BW Server Release >= 2.0A: Source system: Activate.
Manually i tried to push the idocs in the BW and source system using TRF but i dint found any records???
Soruce system connection is fine. Profile parameters are set properly and its active .. But still am getting the same problem.
Many thanks, I'll applicate your help.!
Rakesh

Hi
I am also facing the same problem. This happened after restoration of the original system with a copy of the production.
I am not able to get the IDOC posted in the source R3 system.
I did a debug and it failed when verifying the table, RSBASIDOC.
There appeared to be some missing records which need to be inserted.
I can't find a way to insert the missing record and since then, I am not able to proceed.
Have you resolved the issue?
can you share how it can be overcome?
Thanks a lot

ALE IDOC reply from other system with other data

Hi
I have a custom program which sends a document from 800 client to 500 client.The custom program should receive the document no which gets created in 500 client.
I mean as soon as i send the data from 800 to 500 ( In 500 the data gets saved and a new doc no. gets generated which should be sent back to the 800 Custom program),user should get a pop with doc no that is generated in 500........
Can anyone pls let me know how i can do this...
Regards
Sajid

Hi Shaik,
You are sending document from client 800 through idoc, you put this idoc number in BD87, here you can the partner idoc number as well as status of partner idoc which created in client 500.
Same you can verfiy after checking the partner idoc number in EDIDS,EDID4 tables in client 500. From here u can write a logic to show pop up for the document number.

Condition types from SRM system t backened system

Hi,
We are using SRM 7.0, we have decided to go ahead with the pricing proceedure and the condition types which are there in ECC the same should be replicated to SRM.
We have created the same pricing proceedure and the calculation scheema in SRM.
Now my requirement is when i create a PO with the conditions and when i am transfering to ECC the PO should also be with the condition types. It should be a similar PO in ECC.
Is this can be addressed.

Hi
I wish to update on this further:
Under Copying rules for Conditions, for Source table 350 (Sales Organization), I am maintaining report "RV15CC03" which is material to material.
I think I need to use something different since I am copying data from Sales Org to Sales Org.
I don't find a suitable program for Sales Org here.
Any ideas on how to go about.
Thanks
Satya

QRFC/TRFC for sending idocs from SAP system to XI

Hi experts,
The standard program RFFOEDI1 generates payment orders - first PEXR2002 and then EUPEXR idocs. These idocs are to be sent to the bank from SAP through XI. Bank partner profile is maintained. But these idocs because of TRFC are not getting sent in the order in which they are generated by the SAP system. So I changed the bank partner profile settings from TRFC to QRFC and gave the rule name as first 16 of mes type. But the idocs are struck in the SAP system. Is there any standard program to be run to send the idocs out from SAP system or is it automatic.
Please suggest a standard method which is to be followed to send the idocs in the same order in which they are getting generated for the scenairo above.
Regards,
Asha

Hi Asha,
As you said Idocs are stucking,
To send Idocs to XI, you must have maintain some settings in XI to receive Idocs. Once they are done properly .in R3 side standard way to send idocs to XI is Maintaining Change Pointers and shedule the programe to trigger that most of Standard idocs will have standard programs to catch change pointers and send them to external system.
and to maintain the same order of idocs there is a setting called Quality Of Service in XI side ,that option should be set to Exactly Once In Order .
Regards,
Ramesh.

Send IDOC from SAP system to IX but can't see any message in SXI_MONITOR

Hi all,
I have built up an XI system and configured an IDOC to IDOC scenario between two SAP Systems. After completed all configuration necessary:
1. Configuration on Source Side (SAP System that send IDOC) and on Target Side (SAP System that receive IDOC) is OK.
2. SLD is OK: Technical System and Business System are correct for these two SAP System.
3. Integration Repository: all designed Object is OK.
4. Integration Directory: all configuration is OK. "Test Configuration" Function is OK.
5. Runtime WorkBench: is OK. "Test Message" Function of "Integration Server" is OK.
In general, it is all OK.
But when i send an IDOC from SAP System Sour Side (Outbound IDOC from Source Side is OK), on the XI server i can't see any message in Tcode SXI_MONITOR. In this case, my XI server didn't receive any IDOC Message from this Source Side, and so that my XI server can't process and exchange any IDOC sent from Source Side.
Anyone can please help me to explain this problem: why my XI server can't receive any IDOC message from SAP System Source Side when all configuration is OK? Do anyone see the same case as this case?
Thanks a lot for all in advance,
Best regards,
Vinh vo

Hi,
Possible checks
At R/3 side
1) Check in SMQ1 and SM58
At XI Side
1) Check in SMQ2 and IDX5
Check this
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/frameset.htm
Regards
Seshagiri

ALEREQ idoc type from PI system

Similar Messages

Maybe you are looking for