Trnsporting of iboun and outbound Idoc interface to QA and PRD systems

Hi,
We have successfully completes the developement of our File to/From Idoc scenarios on Dev environment. Can some tell me how can I transport these to QA and PRD systems? How about the WE21 BD54(On Bus Sys) IDX1 and IDX2 configurations transports? Do we need to do them searately on each of the systems? Or they are transfereable too?
Thanks.
Sri.

There are two ways to Transport XI objects-
1) File Import/Export -- Simple and easy.
2) CMS
CMS is somewhat standard way to do. Becuase you can track the objects. But for this you need to install the CMS separately.
just go thru these quick links-
http://help.sap.com/saphelp_nw04/helpdata/en/e1/69a740aa053a13e10000000a155106/frameset.htm
XI Software Logistics Solution III: CMS
Also check in service.sap.com- for how to guides-
https://websmp201.sap-ag.de/nw-howtoguides
The other way is using CMS. Refer to following series of blogs for step by step process.
XI Software Logistics 1: SLD Preparation
XI Software Logistics II: Overview
XI Software Logistics Solution III: CMS
Refer to how to guides for setting up CMS.
https://websmp106.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&
1. WE21 -- Creating Port--.
Yes. You can do them separately in individual system.
2. BD54 -- Logical system. You can create in individual system or you can transport the table having logical system entry i.e. TBDLS and TBDLST.
Hope this will help.
Nilesh

Similar Messages

Outbound IDocs are not visuible in Middleware system(SeeBeyond)

Hi Experts,
We need need your expertise help on this issue.
Issue:
The Outbound IDocs which are in status 12 in SAP system are not visuible in Middleware system(SeeBeyond) for customized message type( forecast -ZFOSHT)
If we create a IDoc by using customized program, IDoc(eg.0000000012345678) is successfully created and the status of IDoc is 12. but not visible in Seebeyond.
but If we are re sending the same IDoc(0000000012345678) through WE19(IDoc creation) without changing any thing,the newely created IDoc reached to the Seebeyond.
Please look the issue and help me on this.
Raghavendrarao.R
+91 9739006564

Hi,
After your Function module for IDoc creation either it is Z function module or standard one "MASTER_IDOC_DISTRIBUTE" write these
CALL FUNCTION 'DB_COMMIT'.
CALL FUNCTION 'DEQUEUE_ALL'.
COMMIT WORK.
This should solve your problem.

How to add EP(DEV and QAS and PRD systems in solution manager)

Dear Gurus,
I want to include EP dev and qality and prodution systems in solution manager .
While installation of EP(only ASJAVA it is not having ASABAP) i selected solution manager as a Central SLD. But i deleted the systems in solution manger and recreated it again. I created all the systems and datatabae and logical components but in maintenane optimizer it is showing only production system but it is not showing development and quality systems in maintenance optimizer.
How to see developmnet and quality systems in maintenace optimizer.
Same thing for ECC also.
ECC dev and quality systems installed in the same server.
In maintenace optimizer it is showing only dev sysetm it not showing quality sysetm.
Can any body help this probelm.
Thanks & Regards
Rao.

I think you need to adjust your filter settings in the initial screen of MOPZ.
It's in the right top corner.

Different Recipients of Alerts in DEV and PRD Systems.

Dear All
I wanted to know if it is possible to configure different set of recipients for an alert category in XI DEV and XI PRD systems.
For example i have two groups "Group A" and "Group B" which should recieve alert mails.For this ,
we can create 2 different roles in XI DEV i.e. "Role_A" and "Role_B" and assign user id's to these roles and then assign these roles to Alert Category using the "Recipients Via User Roles" option .This is done in XI DEV system.
My question is it possible that alert mails are just sent to "Role_B" in the XI PRD system. (not to ROLE_A). As ideally we would be transporting the alert categories from DEV> QAS> PRD can we have different recipients configurations in DEV and PRD.
Please suggest.
regards
Nilesh.

Hi Nilesh,
Yes it is possible, Just change the receipent of alert category on PRD system (you can change receipent anytime you want).
Regards,
Gourav
reward points if it helps you

Wage type characteristics variation in Dev and PRD system

Hi All,
We have a wage type for ex: 9501, We will be entering the WT in infotype 15 and the in the payslip it will be in payments section.
When I enter value 50 in DEV system, it is showing 50 in payslip under payments section but in PRD system the same scenario reacts as 46.53 in the payslip when we enter 50 in infotype 15. Not sure why it is behaving in such a way, any ideas?
With Regards,
Giriesh M

Hi Sikindar,
Thank you for the respond. I have checked where it get changed and it was happening in GVAL. Later I find out that it is based on /801 splits ( it has 2 splits and based on the first record it was producing such result). As I am new to functional side it is bit struggle to know from where I have to analyse. Your suggestions helped me to find out. Thanks a lot.
With Regards,
Giriesh M

Outbound IDOC not received at the receiver system.

Hi,
Im sending an IDOC from sap to a non-sap system. During this process, from sap system it is executing successfully without any erros and the status is also '03' .
The problem is that the other system is unable to receive the IDOC sent from SAP system.
The connection is like TCP/IP and the registered server program is given as 'PROGRID' in RFC destination.
I would like to know what would be the possible cases where this IDOC is not received at the receiver system.
The configuration is perfect as per my knowledge. Just want to confirm one thing 'do i need to include any message type such as "SYNCH".
Awaiting for your solutions.
Thanks
rohith

Hi,
If the IDOC is sent successfully from the sender system then the status of the IDOC will be '03' , no matter whether the receiver has received the IDOC or not.
As per your case,
Check the Partner Profile parameters , whether the basic and extended message types are used properly.
The message type Synchron (Sync) is generally needed in Inbound IDOC side. Check whether you have added SYNCH or not.
Hope this Helps.
Regards,
Abhinab Mishra.
Experience is the name everyone gives to their mistakes.

Risks when maintain only one SolMan system for DEV, QAS and PRD systems

What are the risks involved when maintaining only one solution manager system for entire client landscape(Small size).
Or No risks are involved?
Or Is this the SAP rrecommended approach for small size landscapes?
One SolMan system -> DEV and QAS and another SolMan system -> PRD.

>
Sanjai Prabu Govindan wrote:
> What are the risks involved when maintaining only one solution manager system for entire client landscape(Small size).
> Or No risks are involved?
Anand: Risks Involved depends on what all aspects\Scenarios the Solution Manager System is used for. It Could be used for the following purposes
1) Service Desk
2) Solution Monitoring
3) System Monitoring
4) Change Management
How do you propose to use the Solman system ?
>
> Or Is this the SAP rrecommended approach for small size landscapes?
> One SolMan system -> DEV and QAS and another SolMan system -> PRD.
Anand: This is the most idealistic and SAP recommended way of using Solman....it always better to have it this way no matter in how many scenarios you intend to use Solman for....
Regards,
Anand.....

OSS Patch Comparison between DEV and PRD systems

Hi All,
Can you provide me the steps how to compare SNOTE applied in BI Development and BI Production.
Thanks & Regards,
Jelina

check this
OSS Note Patch Implemented?
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/472443f2-0c01-0010-20ab-fbd380d45881?QuickLink=index&overridelayout=true

Setup: IDOC Interface FIDCCH

Hello,
We are curreently setting up an OUTBOUND IDOC interface regarding Billing Document Data.
We are using Mess Type FIDCC2
I have set up the distrubution model (BD64) as well as done the IDOC customizing settings ( WE20/WE21 ... ), and 'Cross System Company Code customzing ( 0B72, OBV7 ... )
Everything is working fine when creating the billing document. ( An IDOC of type FIDCC2 is triggered correctly )
However we need to send the changes as well.
I have seen that there exists a message type FIDCCH.
I did exactly the same steps like I did for FIDCC2.
Howvere changing a billing doc ( FB02 ) does not trigger an FIDCCH IDOC.
What do I still need to do to enable the sending of IDOCS of type FIDCCH (extra ico FIDCC2) ?
Best regards,
Erwin

Nope we did not get this resolved.
But apparently they will normally not make any changes to FI documents.
It is possible however to 'create' a document to 'cancel' te previous one, but that is also a 'create'
Regards,
Erwin

Procedure to Error Out Outbound IDocs

Hello,
         I have a Requirement in which I am using ORDERS05 IDoc Type and extended it to ZORDER05 to populate Custom Fields and sending the Purchase Order Outbound IDoc to the Vendor from SAP System. Now, my requirement is that if any of the Custom Fields are not maintained in SAP and not populated in the IDoc, I need to Error Out the IDoc with Error Status 26. I am currently working on the SAP ECC 5.0. I have implemented similar Error Handling Mechanism earlier by using Enhancement Framework as I was working in ECC 6.0 environment where I've added the Code by Creating an Enhancement Implementation in the Function Module IDOC_CREATE_ON_DATABASE. But since ECC 5.0 does not have the Enhancement Framework feature, please let me know how to achieve this.
Thank You,
Venkata Phani Prasad K

Hi
why don't you try using the standard method for validation of data?
By implementing the customer-function EXIT_SAPLEINM_002 or BAdI MM_EDI_ORDERS_OUT you can make checks of completeness of the idoc segments (in your case, additional custom data) and, if they were not complete, report an error message raising the exception DATA_NOT_RELEVANT_FOR_SENDING
ie
if <Idoc Custom Field> is initial.
MESSAGE ID 'S1'
               TYPE 'E'
               NUMBER '333'
               WITH Additional data are incomplete'
               RAISING data_not_relevant_for_sending.
endif.
Thus you have the evidence of the error in the processing log of the output message while the IDOC is not created.
The solution works very well and is not invasive.
Regards.
Andrea

Outbound IDoc status set as 31

Hi Friends,
I am working on the outbound IDoc interface IDOC_OUTPUT_ORDRSP. I modify/add few segments based on the business conditions using the user-exit EXIT_SAPLVEDC_003 (ZXVEDU15). According to the business need, I have to set the IDoc status record as 31. Now IDoc is being created with status record as 30. Is there any way to set the status record with status 31 within the scope of this IDoc interface IDOC_OUTPUT_ORDRSP.
Pls let me know if any user exit for this same purpose. If not possible to set status explain me the reason for that.
Thanks
Hari

Hi,
You can use this standard program RC1_IDOC_SET_STATUS to change IDoc status 30 to another status.
If the program does't exits then try this ...
DATA: L_EDIDC_TAB       LIKE EDIDC      OCCURS 1 WITH HEADER LINE,
      L_IDOC_STATUS_TAB LIKE BDIDOCSTAT OCCURS 1 WITH HEADERLINE,
      L_IDOC_CONTROL    LIKE EDIDC.
    L_IDOC_STATUS_TAB-DOCNUM = <your IDoc number>.
    L_IDOC_STATUS_TAB-STATUS = '68'.
    APPEND L_IDOC_STATUS_TAB.
    CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
         EXPORTING
              IDOC_NUMBER               = L_EDIDC_TAB-DOCNUM
         IMPORTING
              IDOC_CONTROL              = L_IDOC_CONTROL
         TABLES
              IDOC_STATUS               = L_IDOC_STATUS_TAB
         EXCEPTIONS
              IDOC_FOREIGN_LOCK         = 1
              IDOC_NOT_FOUND            = 2
              IDOC_STATUS_RECORDS_EMPTY = 3
              IDOC_STATUS_INVALID       = 4
              DB_ERROR                  = 5
              OTHERS                    = 6.
<b>Reward points</b>
Regards
Message was edited by:
        skk

Requirement for Alert when outbound idocs are failing

SAP A -
IDOCS -
> SAP B
We currently have a SAP A system sending outbound idocs to SAP B system via ALE. The current issue is when SAP B system is down. The outbound idocs being sent from SAP A system fail.
We want to get a alert when the System B is down.
What are the options available in SAP to achieve this requirement.
Thanks in advance for any inputs that will be provided.
Regards,
Chandra Kumar

Dear Chandra,
The logical solution to the problem is as below,
You need to have a Function module which checks the RFC connections between two systems before sending idoc. If the connection is found OK then the idoc should be send else a Alert message should be raised u201CSystem B is down, idoc can not be processedu201D
Please let me know if this solution helped in resolving your query.
Regards
Dinesh

To move Interfaces from dev to prd/qas

Hi Experts,
I have created interfaces in XI developement system and now want to move it QAS and PRD system
How should i go for that....do we need to define business system for QAS and PRD and make all the configuration in ID again ?
Thanks in advance.
Vishal

Vishal,
Check this documents for help on this transition:
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
and also this for more info:
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
Regards,
---Satish

Do you allow query or view creation in QA and PRD?

Do you allow queries, views and workbooks to be created in QA or PRD? If so, do you transport those BEx Objects into the other systems (e.g. PRD->QA and PRD->DEV or QA->PRD and QA->DEV)?
Often I find I will be creating a query or a view in QA or PRD because those systems happen to have the data I am required to analyze. DEV does not always have the data available. But how do I move this BEx object to the other systems?
This happens most often to views of a query, but also applies to queries, workbooks etc. Like changing a workbook already transported to production.
Thanks for your input.

Hi Peter,
In our system we (developers) are allowed to create / modify queries in the QA and Prd system. We do not actually 'develop' here, but we have this access for the reason you mention (data availability). The main query development is carried on in the Dev system and transported up, but the change access lets us to quickly solve issues many times. If we do put in a change in teh query, we replicate the change made in the dev system and transport it...no reverse transports are set up in the system.
Hope this helps...

Same SID for QA & Prd systems - pros and cons?

We have the foll systems:
1. Enterprise Portal 7.0
2. NWDI 7.0
3. NW 7.0 (with XECO - Ecommerce)
4. TREX 7.1
5. Content Server 6.40
6. ECC 6.0
Currently the QA and Prd systems have the same SID and system/instance no, although they are on different hosts.
We would like to know what are the long term pros and cons for keeping the QA and Prd SIDs the same for all systems.
We are already making a list, so thought we might as well get more inputs from the community too.
We already have this arrangement for the past 3 months and have not faced any major issues.
A couple of cons though:
1. Cannot use solman as it cannot distinguish between the diff servers with same SID
2. ABAP transports from QA to Prd have to be manually done (cannot use STMS)
Thanks
Prasad

Hi Manoj,
Changing the SID of java systems is a very tedious procedure. Hom sys copy is just a part of the SID change...there are a whole lot of configs to be done after that...the task is eq to a new setup of systems
For once, the efforts put in are huge..you can see there are 5 systems..besides, it will involve coordination from all teams - basis, development, functional, project management.
Here are a few advantages that we know of:
1. No efforts reqd to change back to original SID
2. During disaster recovery, we just have to restore the production database on QA and change the hostname, whereas its not so in case of having diff SIDs
3. For end-users this will be transparent because they will be using the hostname in the URL which is anyways different
We have the same SIDs for the past 3 months and have not seen major issues, but we also would like to know from the long term perspective if there are any risks that we have not foreseen...hence we seek help from the community.
Hope its clear now
Thanks for your response
Prasad

Trnsporting of iboun and outbound Idoc interface to QA and PRD systems

Similar Messages

Maybe you are looking for