SAP Released Custom (Y) IDOC modification

Hello,
I have problem with modification of a custom released segment. I can not cancel its release. Maybe because it was released in the previous version.
I'd delete some existing fields from the structure and add some new ones also. So the problem is I should DELETE some ones not only to add ones.
I am wondering which way would be the better and easiest... Adding an extension .. I have tried to create a new version for a segment but it does not work since the existing fields of the structure remained unmodifiable, so I can not delete them.
Please clarify mind mind how 'Id fix it <removed by moderator>.
Thx.
Peter
Edited by: Thomas Zloch on Mar 8, 2011 12:43 PM - please no "asap"

Hi Debashish,
I have a similar requirement to develop a Custom module for SFTP adapter for SAP PI 7.1 version..
Can you please advise how you build the adapter and please share the document if you have any...
thanks

Similar Messages

Customer Master Idoc DEBMAS

Hi
I kindly ask you how can I send customer master IDOC in full. I am using change pointer and change pointer allows only to be send ,changed fields other fields are filling with '/' character. Is there any way to send this '/' what is in original

Idoc type will change with the SAP release version with changes in the segments. You may see the difference in segments if you Compare DEBMAS01 and DEBMAS06 segments. Always use the Idoc type which of the current SAP Release.

Steps for creating a custom outbound idoc

Hi,
Can u please each and every step wise for the creation of the custom outbound idoc.
Thanks
Kiran Prasad.

friend before posting ur query, try to utilize the search tab in the forum, u can find the answer for ur query if not continue with postings.
Follow this link for step by step tutorial with screen shots
http://www.****************/Tutorials/ALE/ALEMainPage.htm
1. Create an IDOC Type.
The next step is to create an IDOC type by associating the extension type that you created with the Basic IDOC type. This is a simple process:
u2022 From transaction WE30 or WEDI go to Development -> IDOC Types.
u2022 Enter ZDEBMASZ for Object Name.
u2022 Click on IDOC Type.
u2022 Click on Create.
u2022 Enter DEBMAS02 for Basic IDOC type.
u2022 Enter ZDEBMASX for extension type.
u2022 Enter a description.
u2022 Enter.
u2022 You will see a display of the composite IDOC type with all segments, including Z1SADRX (see Figure 3).
It is possible to associate only one extension type with a Basic IDOC type for a given IDOC type. However, you can have multiple new segments in an extension type.
2. Link IDOC Type to Message Type.
The next step is to link the new IDOC type to its corresponding message type. This is important, because this relationship is referenced in the partner profile parameters where you specify the message type and IDOC type to be used for that particular representative system. To link the message type:
u2022 Use transaction WE82, or from WE30, go to Environment -> IDOC Type / Message Type, or from WEDI go to Development -> IDOC Type -> Environment Î IDOC Type / Message Type.
u2022 Click on Display <-> Change.
u2022 Click on New Entries.
u2022 Enter DEBMAS for message type.
u2022 Enter DEBMAS02 for Basic IDOC type.
u2022 Enter ZDEBMASX for extension type.
u2022 Enter your SAP R/3 release number for Release.
u2022 Save.
This data is stored on the EDIMSG table and is accessed by several ALE processes to relate the message type to the IDOC type.
3. Check the IDOC Type.
Before checking the IDOC type for consistency, it is important to perform another step that releases the extension type to the IDOC type:
u2022 From WEDI go to Development -> IDOC Types -> Extras -> Release Type, or from transaction WE30 go to Extras -> Release Type.
u2022 For the Object Name ZDEBMASX and radio button Extension Type, click Yes.
u2022 The extension type has now been "released."
You canât edit the extension type once itâs released. To cancel the release for further editing or deactivation, go to WE30 Î Extras Î Cancel release. The final step in the IDOC extension process is checking the validity of the IDOC type:
u2022 From transaction WE30 or WEDI go to Development -> IDOC types.
u2022 Enter ZDEBMASX for Object name.
u2022 Click on Extension Type.
u2022 From the Development Object menu select Check.
u2022 Repeat the operation for IDOC type ZDEBMASZ.

How to extract data from custom made Idoc that is not sent

Hi experts,
Could you please advise if there is a way how to extract data from custom made idoc (it collects a lot of data from different SAP tables)? Please note that this idoc is not sent as target system is not fully maintained.
As by now, we would like to verify - what data is extracted now.
Any help, would be appreciated!

Hi,
The fields that are given for each segment have their length given in EDSAPPL table. How you have to map is explained in below example.
Suppose for segment1, EDSAPPL has 3 fields so below are entries
SEGMENT          FIELDNAME           LENGTH
SEGMENT1         FIELD1                   4
SEGMENT1         FIELD2                   2
SEGMENT1         FIELD3                   2
Data in EDID4 would be as follows
IDOC           SEGMENT                          APPLICATION DATA
12345         SEGMENT1                        XYZ R Y
When you are extracting data from these tables into your internal table, mapping has to be as follows:
FIELD1 = APPLICATIONDATA+0(4)        to read first 4 characters of this field, because the first 4 characters in this field would belong to FIELD1
Similarly,
FIELD2 = APPLICATIONDATA+4(2).
FIELD3 = APPLICATIONDATA+6(2).
FIELD1 would have XYZ, FIELD2 = R, FIELD3 = Y
This would remain true in all cases. So all you need to do is identify which fields you want to extract, and simply code as above to extract the data from this table.
Hope this was helpful in explaining how to derive the data.

How Can I transfer invoice details to customer through IDOC in EDI

Dear Sir,
I have some requirements That I want to Transfer Invoce To My Customer In EDI.so how can I do that .I have no Idea Plz Help Me and give the Details Steps with TCODES.

Hello Anil
There are not any transactions available. What you need to do is to convert your IDoc to the EDI message format of your customer (e.g. EDIFACT, TRADACOM, etc.). Usually the mapping process looks like:
SAP R/3 sends IDoc -> converted to IDoc-XML (e.g. by using SAP-XI) -> XSLT mapping to EDI-XML -> convert to EDI file using EDI converter
You may have a look at <a href="http://www.mendelson-e-c.com/">Mendelson (EDI conversion)</a>
Regards
Uwe

IDoc Scenario SAP ERP - PI(Receiver IDoc Adapter) - IDoc to Third-Party system

Dear All,
I have created a scenario to send IDocs via PI system (PI 7.1) to a third party system.
There is no message mapping involved(Only ID part)
I have imported Idoc Metadata from the source ERP system.
Created an RFC destination(BC_ERP_SEA) in the PI system of type TCP/IP with registered Server Program to third party system.(Tested success)
Created a port in IDX1 BC_ERP_SEA with above TCP/IP destination.
Receiver communication channel of type IDoc is created with the following parameters:
         RFC Destination: BC_ERP_SEA
         Segment Version: 640
         Interface Version: SAP release 4.0 or Higher
         Port: BC_ERP_SEA
         SAP Release: 640
Now when I execute the scenario, I get the following error in SM58 of PI system.
Bena IDOC_INBOUND_ASYNCHRONOUS not found on host.
Request your help for this issue.
Thanks,
Jishi

Hi,
Check below steps..it may resolve your issue
1. It is mandatory to specify Ack Destination value in IDoc_AAE sender channel. The value should be an RFC destination name which is connecting to your SAP ECC system.
2. In inboundRA resource adapter, the value for the property "local" should be set to "true".
Regards,
Tulasiram.

Unable to cancel release of an IDOC

Hi All,
I am trying to cancel release of an IDOC that I developed in 4.6C environment. We are now on ECC6 environment and when I try to cancel release it gives me an error "Can not unclose segment: release of last version is not SAP-version". Has anyone ever experienced it? How can I resolve it?
Thanks for your help.
Regards.

Hi,
Do you remember how you did it?
Many Thanks!

How to maintain SAP Release status in table COTPL

Hi All,
We have upgraded our system from ECC EHP4 TO ECC EHP 5. Now our SAP Release is 702 but in table COTPL
still the SAP Release status is 701 becuase of which there is error in some of our sap jobs.
Request you all to help us. How we can maintained SAP Release in table COTPL?
Thanks

Hi,
You can try using priority field in the rule. Please check this.
Priority for Responsibilities
If you are using responsibilities for role resolution in Workflow, you can provide individual responsibilities with priorities.
Example: There are various responsibilities for a standard role for processing orders, grouped, for example according to order value (one responsibility for orders up to a certain value, another for orders with a greater order value).
Assuming that orders for a particular customer are always to be processed with the same responsibility (and therefore by the same agent), you can access it via another responsibility with a higher priority that contains the customer name as the only criterion. The responsibility (-ies) with lower priority, and therefore the order value, is then no longer taken into account during agent determination.
Use only numeric values here, and note that, logically, the responsibility with the highest numberic value in this field has the highest priority.
Procedure
1. Sequence Priority of Objects
In Create mode, assign a priority to the objects you wish to rank.
To do so, assign an alphanumeric value (1, 2, 3... or A, B, C...) to each object.
In Change mode, overwrite the value in the field.
2. Priority When Defining Evaluation Paths
In the Priority field, enter the priority or priorities for objects that should be considered in evaluation paths. Enter "*" if you want to have no restriction.
3. Priority for Responsibilities
Maintain the priority directly in the detail screen for the responsibility or in the overview screen for the responsibilities for the rule. Note that you must use numeric values here. On the overview screen, the system sorts the responsibilities in descending order of priority.
Hope this helps.
Feel free to revert back.
-=-Ragu

Custom inbound Idoc error handling/ Workflow

Dear Experts,
I have a requirement where in I created a custom inbound idoc, but now i need to handle the errors in the workflow and notify the users thru workflow on an error.
Can some one please provide me a step by step guide on how to create a organizational unit, position and assign users to the position... and any other steps that need to be configured to notify the user on the error.
I'm pretty new to all these organizational uints and workflow related stuff. Any step by step would really be helpful.
Thanks for your time.
-Amit.
Moderator message: sorry, these forums cannot replace proper training, if there is step by step guides out there, then please use the search functions.
Edited by: Thomas Zloch on Oct 31, 2010 11:50 AM

Vittal,
1. If your requirement is for a SAP Standard Basic Message type and a Z extension: Then you simply have to find out the 'Standard Task' associated with basic type. You shouldn't worry about extensions. The standard task will be triggered at input error.
2. If your requirement is for a Z basic type i.e. you have created a customer IDOC for a custom processing: There are many dependencies on how you can achieve this. Firstly, you need to know how you're are processing this Z_IDOC. Are you using a standard FM or custom workflow or custom FM? There should be some triggering event within the processing of this Z_IDOC which will raise a certain flag when the error you want to capture happens (or when there is a generic error). You can configure this event in binding objects to trigger a workflow task. If you take a look at any standard tasks, you'll get an idea how the triggering event happens.
Once the workflow task (you can use custom task or use a standard task i.e. by triggering a standard event within the IDOC processing program) is triggered, you can either send it to SAP inbox, e-mail, trigger another processing etc. This is altogether another story.
So bottomline: For custom IDOC processing, you need to trigger an event when error happens. This can be a custom event or a standard event. This event should be linked to a task (custom/standard - check in SWETYPV). Bind all of these in PFTC. Once the task is triggered, you can do whatever you want to do with it.

CIN installation on ECC6 SAP system upgrated from 4.6C SAP release

Hi all,
We have a ECC6 SAP system upgrated 4 years ago from a 4.6C SAP release system. In the old SAP release we don't have installed CIN 40A for India localization, and now we need to have this functionalities has we have to do a rollout on SAP for one indian company.
Problem is that we don't have found any OSS note that explain clearly what we have to do to have in our ECC6 SAP system CIN functionalities.
After application of support packages on level 17 (up minimum required by OSS note 1175384) we have launch function j_1bsa_component_check but we have exception that country IN isn't installed.
We can't use transaction O035 as we have a SAP system already customized.
Thanks in advance for any help or useful information someone can do us about this problem.
Sorry if this couldn't be the right forum to post this type of message, but is't difficult for me, in this particular case, to find the right forum for this type of question.
Regards
Gianpaolo
Edited by: Gianpaolo Papa on Oct 22, 2010 9:55 AM

No asnwers

Why customer master idoc named like DEBMAS?

hi,
i am just curious know why customer master idoc named like DEBMAS?
vendor master data idoc as cremas?
any German abbreviation or English abbreviation behind this will be appreciated.
thanks & regards
Raja
Message was edited by:
Raja

To my knowledge I do not think that the naming has anything to do with the German translations since in German:
Customer = Kunde and
Vendor = Verkäufer....
However the naming has some connection with the Business Case behind customers and vendors. In SAP, a customer is a business partner whose account you debit for money, hence the name DEBMAS and a vendor is a business partner whose account you credit money, hence the name CREMAS.
PS: Reward points and close the question if you find this helpful.
Regards.

Itegration with Websphere Message Broker and Customer Master IDOC

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;
Similar issue has been answered at -Steven Chan blog*
From blog:
Hello, RM,
I have not seen any Oracle-produced documentation along those lines. I don't think there are any Oracle teams that are investing in producing documentation for IBM WebSphere.
I would suggest contacting IBM to see whether they have produced any WebSphere-specific documentation.
Regards,
Steven
Referance:
http://blogs.oracle.com/stevenChan/entry/ebusiness_suite_release_1211_now_available
Ps: You can rise SR for your issue also
Regard
Helios

Check Connection of Communication Arrangement for SAP ERP Financials Using IDoc Failed

Dear experts,
We are checking outbound connection from C4TE to ERP in Communication Arrangement for SAP ERP Financials Using IDoc Failed.
We get the attached error message:
Checking connection failed
Error accessing service; Service Ping ERROR: Forbidden (403)
What could be the reasons, in ERP side, through Tcode SMICM, we didn't see any log from C4TE side, and we cannot ping the ERP side successfully.
One more thing, in C4TE, we tried to set the connection to an SAP internal ERP system, and the connection was successful. But when relinked to the customer ERP system, connection failed.
Could it be firewalls reason?
Thanks!
Best regards,
Wendy

Hi Wendy,
Yes the assumption could be one reason as well for the error (403 forbidden), but there could be several other aspects also to get the 403 error, for better understanding the reason for the error, may I request you to create an incident send it to us.
Also please try once running the scenario in C4T and check if the relevant documents are being sent through Outbound Service or not.
Thanks & Regards,
Bharath

Convert custom outbound idoc to CSV file

Hi
I need to send generate a flat file that will be sent to a non SAP partner. A requirement is that the messages go via the IDOC system. This makes it possible to resend them if necessary.
So there are 2 stages
1) create IDOC. I have done this
2) read IDOC and convert to flat file
stage 1
=====
I have defined a custom IDOC, partner profile etc and developed a Function Module to create the outbound IDOCs The FM is triggered by a message in the NAST table. . This works OK.
So I now have custom outbound IDOCs in the DB with status 30 (ready for dispatch) (WE05).
Stage 2
======
Now I want to convert these custom IDOCs into simple flat files (CSV like).
How do I go about making this happen? I guess I need to develop another Function Module. But I dont know how to tie this FM into the system. My questions are:
How will the FM be triggered
what is the interface of the FM
will I need to configure a 2nd partner profile for stage 2 (which is fine)
Peter
Note1 - there is no EDI converter available so must solve this in ABAP
Note2 - I do not want to create the flat file at the same time as I create the IDOC. This would defeat the purpose of going via IDOCs

No, EDI is only one method of transferring data. There's no need for an EDI subsystem in this case.
To the OP, since it seems the you have decided that you must use IDOC processing in this case, I would go ahead and use a file port (or an XML port). You will drop an IDOC formatted flat file into the specified location (for each IDOC, based on your logical file definition). For you, this will merely be a temporary holding location. You can then use a simple program to read the file, re-format it, send it, then move the original file to a 'processed' location. Of course, you could also just throw away the generated files and read the IDOCs directly with the standard functions available and (re)generate/send the files as required.
It's often done this way with 3rd party EDI providers, where the company in question is required to use EDI by their customers but do not have the required systems in place.

SAP release Timeline

Hi,
I am trying to draw a timeline (just release year is fine) with SAP releases..
from SAP R/2 --> SAP Netweaver 7.10 (7.10 is the last one, isn't it?)... passing through 3.0 4.6C 4.6D 6.10 etc etc
any useful links?
thx
ivan

4.6c
First Customer Shipment      Available      03.04.2000
General Availability      Available      29.05.2000
4.7 1.0
Release to Customer      Available      15.07.2002
Default Release      Available      13.01.2003
4.7 2.0
Release to Customer      Available      22.09.2003
Default Release      Available      02.04.2004
ERP 2004
Release to Customer      Available      21.06.2004
Default Release      Available      28.02.2005
ERP 6.0
Release to Customer      Available      24.10.2005
Default Release      Available      06.06.2006
Check www.service.sap.com/pam for further details..
Award points if found helpful..

SAP Released Custom (Y) IDOC modification

Similar Messages

Maybe you are looking for