Idoc version is changed

Hi evryone,
Someone know if in ECC 6.0 the idoc's structure are changed or not from 4.7 ? the custumer said that INVOIC2 is changed in ECC 6.0
thanks in advance
Moderator message: please do some research before asking, e.g. check the version history of the segments of INVOIC02.
Edited by: Thomas Zloch on Mar 11, 2011 10:52 AM

If you wish to set the PDF version to something other than the current version fo the library, use PDDocSaveEx() (I think that's the call), which gives you an entire parameter block of options including the version.
NOTE: If you are actually modifying the PDF, you should consider if any of the operations that you are performing will introduce newer features into the PDF than those currently present and if so, then adjust the PDF version number accordingly.
Leonard

Similar Messages

Creation of Idocs from the change pointers by the program RBDMIDOC

Hello,
I'm Creating Idocs from the change pointers by the program RBDMIDOC.
The IDOCS Created using the message type HRMD_A are Correct but when i try to RUN RBDMIDOC for message type HRMD_B no Data is selected for distribution.
All the customizing are similar and i presume that all the change pointers are active (BD50 and IMG->Personnel Management -> Organizational Management -> Basic Settings -> Activate change documents).
Can anyone help me with the necessary steps to create this IDOC types.
Do anyone know if the RBDMIDOC report is the Same for messages HRMD_A and HRMD_B.
Thanks in Advance,
Pedro Ferreira

If the setting is fine, there may be some code in exit or badi for program RBMIDOC. Check the Exit and BADI.
check the exit EXIT_SAPLBD11_001 and
check the badi IDOC_CREATION_CHECK.
Probably there may be some code on these exits which are stoping your code from getting generated.These are the two trigger happen once u execute the RBMIDOC program.for HR, we use RHALEINI program to generate the idoc. but even RBDMIDOC works. These 2 triggere will come with RHALEINI also.
If there is no code here, Then there is problem in the setting only.

Idoc trigerring with change pointer under conditions

Hello dear experts
Could you please tell me how can i trigger an outbound idoc using the change pointer ( RBDMIDOC program)?
I have to generate the ARTMAS outbound idoc ONLY when the material status which is the table MARA is set to a certain value.
I can manage to trigger the outbound idoc but i did not manage to restrict this triggering according to the value of the material status fields.
Thanks for all your answers.
Best Regards.
Yannick

I tested using filter on Dist Wh and change pointers - for us, Dist Wh filter for material set on plant. When we made change to matierial, only if change to plant was made, so plant was included in idoc segment, did the filter work. If change material description, plant not on idoc segment so was sent . Looking for alternative...

Any FM/methods to update idoc segments without changing idoc status

Hi All,
My requirement is a reprocessor program which fills up some fields in the idoc segment before posting. So, after updating the segments, the idoc status should remain as before.
Is there any function modules or methods to update idoc fields in segments without changing the idoc status?
I have tried the FMs EDI_DOCUMENT_OPEN_FOR_EDIT, EDI_CHANGE_DATA_SEGMENT and EDI_DOCUMENT_CLOSE_EDIT, but it changes the idoc status.
Thanks,
Arun Mohan

As for FM to do this, i don't know if there are any, but i think you can go directly to the tables with the IDOC data and change them without triggering the changes in status like FM do. Still, i am not sure this is completely true, but you could give it a try. Also, i don't know if this is the best way to do it, because of those legal/audit questions mentioned by Thomas.
Here is a sample code of a program we have to change a field in a segment of WPUUMS.
*& Report YRE00021INTPG
REPORT yre00021reppg.
TABLES: edid4 ,
        edidc ,
        mean .
* Variaveis Auxiliares
DATA: t_edidc TYPE edidc OCCURS 0 WITH HEADER LINE.
DATA: t_edid4 LIKE edid4 OCCURS 0 WITH HEADER LINE .
DATA: BEGIN OF t_docs OCCURS 0,
        docnum LIKE edidc-docnum ,
      END OF t_docs.
DATA: wa_e1wpu02 LIKE e1wpu02 .
DATA: wa_e1wpu03 LIKE e1wpu03 .
DATA: t_itedidd LIKE edi_dd40 OCCURS 0 WITH HEADER LINE ,
      t_itedidc LIKE edi_dc40 OCCURS 0 WITH HEADER LINE ,
      fw_itedidc LIKE edi_dc40 ,
      fw_itedidd LIKE edi_dc40 .
DATA: l_matnr TYPE mara-matnr,
      l_tam TYPE i.
DATA: l_idoc_number TYPE edidc-docnum.
* Ecran de selecção
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_docnum FOR edid4-docnum ,
                s_credat FOR edidc-credat DEFAULT sy-datum ,
                s_cretim FOR edidc-cretim .
PARAMETER:      p_mestyp LIKE edidc-mestyp DEFAULT 'WPUUMS' ,
                p_status LIKE edidc-status DEFAULT '51' .
*SELECTION-SCREEN SKIP.
*PARAMETER:      p_ean11 TYPE mean-ean11.
SELECTION-SCREEN : END OF BLOCK b1.
AT SELECTION-SCREEN.
IF p_status <> '51'.
    MESSAGE e001(yre) WITH 'Apenas pode modificar IDOCS com erro'.
ENDIF.
IF p_mestyp <> 'WPUUMS'.
    MESSAGE e001(yre) WITH 'Apenas pode lançar WPUUMS'.
ENDIF.
*AT SELECTION-SCREEN ON p_ean11.
* SELECT SINGLE * FROM mean WHERE
*    ean11 = p_ean11.
* IF sy-subrc <> 0.
*    MESSAGE e001(yre) WITH 'Ean não existente'.
* ENDIF.
START-OF-SELECTION.
SELECT docnum INTO TABLE t_docs FROM edidc
                     WHERE status = p_status
                     AND   mestyp = p_mestyp
                     AND   docnum IN s_docnum
                     AND   credat IN s_credat
                     AND   cretim IN s_cretim .
CHECK sy-subrc = 0 .
LOOP AT t_docs.
    CLEAR : wa_e1wpu02.
    SELECT * FROM edidc INTO TABLE t_edidc
      WHERE docnum = t_docs-docnum.
    CHECK sy-subrc = 0.
    SELECT * FROM edid4 INTO TABLE t_edid4
                  WHERE docnum = t_docs-docnum AND
                        segnam = 'E1WPU02'.
    CHECK sy-subrc = 0.
    SORT t_edid4 BY segnum.
    LOOP AT t_edid4 .
      wa_e1wpu02 = t_edid4-sdata.
      WRITE wa_e1wpu02-artnr TO l_matnr NO-ZERO.
      CONDENSE l_matnr.
*      l_tam = STRLEN( l_matnr ).
*      IF l_tam <= 6.
        SELECT SINGLE ean11 INTO wa_e1wpu02-artnr FROM ytre00004 WHERE
          codcurto = l_matnr.
        IF sy-subrc = 0.
          WRITE : /1 'Código ', l_matnr, ' alterado para ', wa_e1wpu02-artnr.
        ELSE.
          WRITE : /1 'Código ', l_matnr, ' não encontrado na tabela de conversão'.
          CONTINUE.
        ENDIF.
*        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
*          EXPORTING
*            input = p_ean11
*          IMPORTING
*            output = wa_e1wpu02-artnr.
*      ENDIF.
      UPDATE edid4 SET   sdata   = wa_e1wpu02
                   WHERE docnum = t_edid4-docnum
                   AND   counter = t_edid4-counter
                   AND   segnum = t_edid4-segnum .
      IF sy-subrc <> 0 .
        ROLLBACK WORK .
        WRITE: / t_edid4-docnum .
      ELSE.
        COMMIT WORK.
      ENDIF.
    ENDLOOP.
ENDLOOP.
END-OF-SELECTION.

Idoc for PO changes

Hi,
For any new PO created, an idoc is getting triggered automatically and the same is communicated to vendor through portal.
Please let me know how to trigger idoc for any changes / amendments to the purchase order.
regards,
C. ASHOK RAJ

Hi Ashok,
Goto ME20,
Select your vendor
On the right hand side, you will find "Outbound parmtrs."
Select the "Messsage Type" of your Purchase Order.
Double click on it OR press Display button.
In the 'Messsage Control' tab
Add
(1) Application
(2) Message Type
(3) Process Code ME21N
(4) Check the 'Change' option box.
Hope this will help you.
Rewards are useful.

What is the IDOC type for changing PO price in ECC from SNC?

We have configured the consensus finding tolerance check for date and it is working. When we create confirmation from PO worklist by changing the price and the delivery date, it goes for manual approval if the date change is outside tolerance. Once the confirmation is approved by the buyer we are getting two Idocs in SAP. One is ORDRSP-ORDERS05. This one has the new price, but does not change the price in the PO. It only creates confirmation. The other one is PORDCH-PORDCH02. This one does not have the new price. It only changes the delivery date in the PO line item. We want one single IDOC which will change price (if price is changed), change delivery date and create confirmation. is that possible? If yes, what IDOC type would that be?
Thanks for your help.
Soumen

Hi Soumen
Can you please check whether the below settings are available on ERP side
SPRO-MATERIAL MANAGEMENT-PURCHASING-CONFIRMATIONS-SET UP CONFIRMATION CONTROL
select your confiramtion control line
lets say ZICH, select the confirmation sequence on left hand side
for your order acknowledgement,XX
check the field "Price"
and give the allowed tolerance values in fileds
Permitted Price Overrun in % (Inbound EDI/SOA)
Permitted Price Shortfall in % (Inbound EDI/SOA)
Now resend the data.... it will work
ORDRSP-ORDERS05 should work this time
Best Regards
Vinod

ALE: mapping IDoc fields to change document fields - TBD22 for ADRMAS iDoc

Hi,
I am currently try to find a table or way to extract the information of the TBD22 table (ALE: mapping IDoc fields to change document fields) for the iDocs/ Message Types:
ADRMAS
INTERNAL_ORDER
PROJECT
I am looking for a table that shows me to which SAP R/3 tables and fields the segments and fields of the above mentioned messages will be mapped to.
When I add one of the above mentioned message types to the table TBD22 selection criteria I always receive the notification: "No table entries found for specific key".
Could anybody determine Which table I have to use or why I cannot extract this information?
Thanks in advance!
Best regards

Hi,
Since we can not map the target IDOC when any of the field changes using nodefunctions , you can write UDF and check the same i.e if field1 changes or field2 changes or field3 changes then trigger new IDoc. This is one of the options that you can try...please try it once.
Regards
Priyanka

Can anyone send me link of IDOC gentn using change pointers!

Hey guys I need to learn IDOC generation using change pointers.Please send me some help notes and link and sample program on that !

Hi,
Change pointers are the mechanism through which you can send data to another SAP system or external system if there is a change happening to specific fields of master data.
For more information, please check this link.
http://www.angeli.biz/www5/cookbooks/workflow/workflow_30/docu.htm
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
Regards,

Changing filed name description - idoc segment creation/change

HI,
is it possible to change the fieldname description in an IDoc Segment without changing the DataElement ?
Exampel:
I Used CHAR40 as dataelement for my own ZZFIELD. In the Idoc the fieldname description of the data element CHAR40 is shown.
Can i change this description ?
thx,
Gordon

No, The IDOC always displays the texts based on the Data Element which is assigned to that field. If you want to display your own text you have two options:
1. Create an enhancement and change the text of the data element which is not recopmmended because it will be changed wherever that data element is used.
2. Instead just create an own data element where you can maintain any texts you need.
Hope that helps,
Michael

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

Idoc Conversion rule, Change pointers and Filters

Hi Experts,
Please any one can help me out, i need material or clear picture about Idoc Conversion rule, Change pointers and Filters where we can use these concepts what is the befit for these concepts.
Thanks in advance,
Ramesh.

Hi,
Check this link. It has got some of the tutorials you are looking for.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Cheers
VJ

Difference between IDOC for creation, change and deletion

Hi,
As per the requirement, an IDOC will be generated for PO, Vendor Masters and Goods receipt when ever a PO or Vendor or Goods receipt is created or changed. How can we identify whether the IDOC has been created for creation or change of a particular thing? Is there any identifier where in we can check whether the IDOC generated is for creation or change?
And also how to identify that a particular PO or VM or GR has been deleted or cancelled?
Thanks & Best Regards,
Phani.

hi,
to check the idoc status ie idoc created or changed --use transaction WE05
we02 to diplay idoc
please rewrd points if helpful,
shylaja

Can we use idoc technique to change or delete the vendor master data?

Hi,gurus,
Can we use idoc technique to change or delete the vendor master data?You know we can create vendor data using idoc CREMAS03 as the receiver adapter,but when change or delete the specified vendor data,must we use RFC adapter technique?
Another question:I found the bapi which creates a vendor master data doesn't have the parameter account group,then we turned to idoc technique.But which adapter should I use when change or delete the vendor data?
Thanks in advance.

Hi,
>>>I found the field of the segment of deletion flag at different level,and very appreaciate your help.
yes - LOEVM - but remember this will not delete the record but only mark it for deletion
>>>It's a long time to wait for your new blog,what new and interesting things do you find?
at least 4 new in my head - 2 simple but important and 2 new + I'd also like to write something for XI guys about
BO data integrator which can also work as EAI tool (BTW I know it's ETL) but how knows when they will appear
Regards,
Michal Krawczyk

Avoid the creation of idoc Debmas with Change Pointers

Hi everybody.
Ive customized the creation of idoc debmas with change pointers.
In BD64 I´ve defined the distribution model but Id like to avoid the creation of the debmas idoc when an specific user has created/modified the custumer data.
How can I get this?
Regards

Hello,
I would suggest to handle this issue with authorization check...
check the authorization object using SU53 and add a separate role for those specific user excluding those objects...
Thanks
K.

Idoc for Material Change

Hi Experts,
The requirement is to receive a standard Idoc for material change and trigger the material creation process in case the material does not exist.
Secondly, what is the Idoc for material change?
Thanks and Regards,
Ravi

Hi,
Go through the following Steps for Creating IDoc Via ALE
ALE IDOC
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
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
1) System Name : ERP000
Description : Sending System
2) 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
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
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)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
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
I know 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.
hope this helps you.
plz reward if useful.
thanks,
dhanashri.

Idoc version is changed

Similar Messages

Maybe you are looking for