IDOC Encryption in the transferring
Hi Buddies,
I use IDOC->XI->IDOC to transfer the sales order through XI. There are some sensitive information in the SO IDOC, so I am wondering there is any way to encrypt the IDOC during the transferring.
Appreciate any reply. Thanks.
B'rgdz. Bu Ju
Hi,
for display encryption you can look at below link
https://cw.sdn.sap.com/cw/docs/DOC-23361
not sure how values will be displayed in PI after transfer.
Encryption at database level is implemented using the BAdI IDOC_DATA_MAPPER and the enhancement spot IDOC_DATA_CRYPT.
If it only needs to be encrypted for display check transaction WECRYPTDISPLAY.
Regards,
Suresh
Similar Messages
-
IDOC creation after the creation of a purchase order
Hi everybody,
I want some configuration details regardign IDOC creation. The requirement is, once i create a purchase order in one system, the details should automatciaclly transfer to other system through IDOC. could any one suggest any document or detailed procedure to accomplish the task. Thanks in advance,
Santosh.hi santosh kumar,
Creating an IDoc Segment WE31:
The segment defines the structure of the records in an IDoc. They are defined with transaction WE31.
We will define a structure to send a text from the text database.
Transaction WE31 calls the IDoc segment editor. The editor defines the fields of a
single segment structure. The thus defined IDoc segment is then created as a data
dictionary structure. You can view the created structure with SE11 and use it in an
ABAP as any TABLES declaration.
To demonstrate the use of the IDoc segment editor we will set up an example, which
allows you to send a single text from the text pool (tables STXH and STXL) as an
IDoc. These are the texts that you can see with SO10 or edit from within many
applications.
We will show the steps to define an IDoc segment YAXX_THEAD with the DDic
structure of THEAD.
To facilitate our work, we will use the "copy-from-template-tool", which reads the
definition of a DDIC structure and inserts the field and the matching definitions as
rows in the IDoc editor. You could, of course, define the structure completely
manually, but using the template makes it easier.
The tool in release 4.0b lets you use both DDIC structures or another IDoc segment
definition as a template.
The thus created structure can be edited any time. When saving, it will create a data
dictionary structure based on the definition in WE31. The DDIC structure will retain
the same name. You can view the structure as a table definition with SE11 and use it
in an ABAP the same way.
Defining the Message Type (EDMSG)
The message type defines the context under which an IDoc is transferred to its destination. It allows for using the same IDoc file format for several different applications.
Imagine the situation of sending a purchase order to a supplier. When the IDoc with
the purchase order reaches the supplier, it will be interpreted as a sales order
received from a customer, namely you.
Simultaneously you want to send the IDoc data to the supplier's warehouse to inform
it that a purchase order has been issued and is on the way.
Both IDoc receivers will receive the same IDoc format; however, the IDoc will be
tagged with a different message type. While the IDoc to the supplier will be flagged
as a purchase order (in SAP R/3 standard: message type = ORDERS), the same IDoc
sent to the warehouse should be flagged differently, so that the warehouse can
recognize the order as a mere informational copy and process it differently than a
true purchase order.
The message type together with the IDoc type determine the processing function.
The message types are stored in table EDMSG.
Defining the message type can be done from the transaction WEDI
EDMSG: Defining the message type (1)
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
IT is as shown .
EDMSG: Defining the message type (1):
The entry is only a base entry which tells the system that the message type is
allowed. Other transactions will use that table as a check table to validate the entry.
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Requirement:
Sales Orders are being created through inbound IDocs using FM 'EDI_DATA_INCOMING'. Now a Report is required to check the status of these Inbound IDocs along with Sales Orders generated against customer Purchase Orders.
Processing:
The report selects, 'ORDERS' IDoc numbers & status, generated between given time range, from table EDIDC. Further, it calls Function Module 'IDOC_READ_COMPLETELY' to get the IDoc details. Then required information is extracted by reading relevant field data of IDoc segments.
sampl code:
REPORT Z_EDI_FILE_LOAD_STATUS_REPORT .
Staus Report for Inbound IDOCs ( Sales Orders )
Program : Z_EDI_FILE_LOAD_STATUS_REPORT
Presented By : www.rmtiwari.com
TABLES : EDIDC.
ALV stuff
TYPE-POOLS: SLIS.
DATA: GT_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
GS_LAYOUT TYPE SLIS_LAYOUT_ALV,
GT_SORT TYPE SLIS_T_SORTINFO_ALV,
GT_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA : BEGIN OF T_REPORT OCCURS 0,
IDOC_NO TYPE EDI_DOCNUM,
IDOC_DATE TYPE SY-DATUM,
IDOC_TIME TYPE SY-UZEIT,
SORDER_NO TYPE VBELN,
STP_NO TYPE KNA1-KUNNR,
STP_NAME(35) TYPE C,
STP_PHONE(12) TYPE C,
PO_NO(15) TYPE C,
STATUS TYPE C,
S_TEXT(70) TYPE C,
ERROR(70) TYPE C,
END OF T_REPORT.
--PARAMETER--
selection-screen begin of block date with frame title TEXT-S01.
select-options: UDATE for EDIDC-UPDDAT
default SY-datum obligatory, "Changed On
UTIME for EDIDC-UPDTIM . "Changed Time
selection-screen end of block date.
INITIALIZATION.
START-OF-SELECTION.
PERFORM SHOW_STATUS_REPORT.
*& Form alv_grid
text
--> p1 text
< -- p2 text
FORM ALV_GRID.
IF GT_FIELDCAT[] IS INITIAL.
PERFORM FIELDCAT_INIT.
PERFORM LAYOUT_INIT.
PERFORM SORT_INIT.
ENDIF.
PERFORM GRID_DISPLAY.
ENDFORM. "alv_grid
*& Form layout_init
FORM LAYOUT_INIT.
GS_LAYOUT-ZEBRA = 'X'.
GS_LAYOUT-CELL_MERGE = 'X'.
GS_LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
GS_LAYOUT-NO_VLINE = ' '.
GS_LAYOUT-TOTALS_BEFORE_ITEMS = ' '.
ENDFORM. " layout_init
*& Form fieldcat_init
FORM FIELDCAT_INIT.
DATA: LS_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_NO'.
LS_FIELDCAT-KEY = 'X'.
LS_FIELDCAT-REPTEXT_DDIC = 'IDOC'.
LS_FIELDCAT-OUTPUTLEN = 10.
Fix for ALV print bug, which puts 'N/A' over last digit
Set inttype to 'N' to stop corruption of printed ALV cell.
LS_FIELDCAT-INTTYPE = 'N'.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_DATE'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Date'.
LS_FIELDCAT-OUTPUTLEN = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'IDOC_TIME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Creation Time'.
LS_FIELDCAT-OUTPUTLEN = 8.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STATUS'.
LS_FIELDCAT-REPTEXT_DDIC = 'St'.
LS_FIELDCAT-OUTPUTLEN = 2.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'ERROR'.
LS_FIELDCAT-REPTEXT_DDIC = 'Message'.
LS_FIELDCAT-OUTPUTLEN = 70.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party No'.
LS_FIELDCAT-OUTPUTLEN = 10.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_NAME'.
LS_FIELDCAT-REPTEXT_DDIC = 'Sold to Party Name'.
LS_FIELDCAT-OUTPUTLEN = 35.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'PO_NO'.
LS_FIELDCAT-REPTEXT_DDIC = 'Purch Order'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
CLEAR LS_FIELDCAT.
LS_FIELDCAT-FIELDNAME = 'STP_PHONE'.
LS_FIELDCAT-REPTEXT_DDIC = 'S.T.Party Phone'.
LS_FIELDCAT-OUTPUTLEN = 15.
APPEND LS_FIELDCAT TO GT_FIELDCAT.
ENDFORM. "fieldcat_init
*& Form sort_init
FORM SORT_INIT.
DATA: LS_SORT TYPE SLIS_SORTINFO_ALV.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_DATE'.
LS_SORT-SPOS = 1.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_TIME'.
LS_SORT-SPOS = 2.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'STATUS'.
LS_SORT-SPOS = 3.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
CLEAR LS_SORT.
LS_SORT-FIELDNAME = 'IDOC_NO'.
LS_SORT-SPOS = 4.
LS_SORT-UP = 'X'.
APPEND LS_SORT TO GT_SORT.
ENDFORM. "sort_init
*& Form grid_display
FORM GRID_DISPLAY.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
IS_LAYOUT = GS_LAYOUT
IT_FIELDCAT = GT_FIELDCAT
IT_SORT = GT_SORT
i_callback_program = SY-REPID
I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
I_DEFAULT = ' '
I_SAVE = 'X'
TABLES
T_OUTTAB = T_REPORT
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2.
ENDFORM. "grid_display
*& Form COMMENT_BUILD
Processing of listheader
FORM COMMENT_BUILD USING P_FK_LIST_TOP_OF_PAGE TYPE SLIS_T_LISTHEADER.
DATA: LS_LINE TYPE SLIS_LISTHEADER.
REFRESH P_FK_LIST_TOP_OF_PAGE.
List Heading : Typ H
CLEAR LS_LINE.
LS_LINE-TYP = 'H'.
LS_LINE-INFO = 'Sales Order Interface: Z_EDI_FILE_LOAD'.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
List : Typ S
clear LS_LINE.
LS_LINE-typ = 'S'.
LS_LINE-key = 'Date Range:'.
LS_LINE-info = UDATE-low.
if not UDATE-high is initial.
write ' To ' to LS_LINE-info+30.
LS_LINE-info+36 = UDATE-high.
endif.
APPEND LS_LINE TO P_FK_LIST_TOP_OF_PAGE.
ENDFORM. " COMMENT_BUILD
FORM TOP_OF_PAGE *
Ereigniss TOP_OF_PAGE *
event TOP_OF_PAGE
FORM TOP_OF_PAGE.
PERFORM COMMENT_BUILD USING gt_LIST_TOP_OF_PAGE[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
IT_LIST_COMMENTARY = GT_LIST_TOP_OF_PAGE.
ENDFORM. "TOP_OF_PAGE
*& Form show_status_report
FORM SHOW_STATUS_REPORT .
Report to show status.
DATA: BEGIN OF T_TEDS2 OCCURS 0.
INCLUDE STRUCTURE TEDS2.
DATA: END OF T_TEDS2.
DATA: BEGIN OF T_IDOC_CONTROL_TMP OCCURS 0.
INCLUDE STRUCTURE EDIDC.
DATA: END OF T_IDOC_CONTROL_TMP.
CONSTANTS: C_STATUS_IN_IDOC_POSTED LIKE EDIDC-STATUS VALUE '53'.
DATA : T_EDIDS TYPE STANDARD TABLE OF EDIDS WITH HEADER LINE.
DATA : T_EDIDD TYPE STANDARD TABLE OF EDIDD WITH HEADER LINE.
DATA : GV_PARTNER_SEG TYPE E1EDKA1,
GV_PO_REF_SEG TYPE E2EDK02.
Get text for status values
SELECT * FROM TEDS2 INTO TABLE T_TEDS2 WHERE LANGUA = SY-LANGU.
Read the IDoc's status after processing
SELECT * FROM EDIDC
INTO TABLE T_IDOC_CONTROL_TMP
WHERE UPDDAT IN UDATE
AND UPDTIM IN UTIME
AND MESTYP = 'ORDERS'.
LOOP AT T_IDOC_CONTROL_TMP.
IDoc has been processed, since control record changed.
READ TABLE T_TEDS2 WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
T_REPORT-IDOC_NO = T_IDOC_CONTROL_TMP-DOCNUM.
T_REPORT-IDOC_DATE = T_IDOC_CONTROL_TMP-CREDAT.
T_REPORT-IDOC_TIME = T_IDOC_CONTROL_TMP-CRETIM.
T_REPORT-S_TEXT = T_TEDS2-DESCRP.
IF T_IDOC_CONTROL_TMP-STATUS = C_STATUS_IN_IDOC_POSTED.
ok status
T_REPORT-STATUS = 'S'.
ELSE.
error status
T_REPORT-STATUS = 'E'.
ENDIF.
Get IDoc details.
CALL FUNCTION 'IDOC_READ_COMPLETELY'
EXPORTING
DOCUMENT_NUMBER = T_REPORT-IDOC_NO
TABLES
INT_EDIDS = T_EDIDS
INT_EDIDD = T_EDIDD
EXCEPTIONS
DOCUMENT_NOT_EXIST = 1
DOCUMENT_NUMBER_INVALID = 2
OTHERS = 3.
Get Error status
READ TABLE T_EDIDS WITH KEY STATUS = T_IDOC_CONTROL_TMP-STATUS.
IF SY-SUBRC EQ 0.
REPLACE FIRST OCCURRENCE OF '&1' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA1.
REPLACE FIRST OCCURRENCE OF '&2' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA2.
REPLACE FIRST OCCURRENCE OF '&3' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA3.
REPLACE FIRST OCCURRENCE OF '&4' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA4.
REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA1.
REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA2.
REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA3.
REPLACE FIRST OCCURRENCE OF '&' IN T_EDIDS-STATXT
WITH T_EDIDS-STAPA4.
T_REPORT-ERROR = T_EDIDS-STATXT.
ENDIF.
LOOP AT T_EDIDD.
CASE T_EDIDD-SEGNAM.
WHEN 'E1EDKA1'.
GV_PARTNER_SEG = T_EDIDD-SDATA.
CLEAR : T_REPORT-STP_NAME.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = GV_PARTNER_SEG-PARTN
IMPORTING
OUTPUT = T_REPORT-STP_NO.
SELECT SINGLE NAME1 TELF1
INTO (T_REPORT-STP_NAME,T_REPORT-STP_PHONE)
FROM KNA1
WHERE KUNNR = T_REPORT-STP_NO.
WHEN 'E1EDK02'.
GV_PO_REF_SEG = T_EDIDD-SDATA.
T_REPORT-PO_NO = GV_PO_REF_SEG-BELNR.
ENDCASE.
ENDLOOP.
APPEND T_REPORT.
ENDLOOP .
SORT T_REPORT BY STATUS IDOC_NO.
Show Report
PERFORM ALV_GRID.
ENDFORM. " show_status_report
thanks
karthik
reward me points if usefull. -
Terms of payment in IDoc E1EDK18 have been transferred: Check data
hi Firends,
In my scenario , i have to convert incoming purchase order to sales order in my system . I am able to get message from partner and idoc is created to the message bt it contains error,
tht is Terms of payment in IDoc E1EDK18 have been transferred: Check data
related to this I had gone through note 388120 - Transfer of conditions and terms of payment.
which says that i have to maintain tht entry in SMME tcode.
My confusion here is, while I tested same scenario in development , and quality server , it was not giving any such error bt in prod system i m gettin this error.
Also if some one knows more details abt this note ,let me know.
Thanks ,
Brijesh SoniHi Brijesh,
you are more likely to get a response for this query if you create a thread in the SD forum.
Regards
Kenny Scott
XI/PI SDN Forum Moderator -
Add segments to an idoc already in the database?
Hi All,
I have a requirement to add segments to idocs that are already in the database. I had hoped to use Function Group EDI1 to do so, but the FM EDI_SEGMENTS_ADD_BLOCK only works for creating idocs from scratch. There is a FM EDI_CHANGE_DATA_SEGMENTS, but it appears to only allow changing segments that already exist, not adding new segments.
How would you handle this one? This is the first time I've been tasked with adding segments to an idoc OUTSIDE of a user exit during create, and I'm unsure how to proceed.
Thanks,
BryanIf it is standard IDoc segment, i am sure you can use this FM
FU EDI_SEGMENTS_ADD_BLOCK
Short Text
EDI interface: Add block of data records
Each call of the function module 'EDI_SEGMENTS_ADD_BLOCK' inserts a block of data records into the IDoc. In each case the EDI interface records the current position in the IDoc and appends the block of records at the end.
The data records are transferred to the function module in an internal table. This table is NOT initialized in the function module, that is, the parent program must carry out an initialization (REFRESH) during a repeated call.
Application data is transferred to the data record. The data record consists of a general administration part and of the field 'SDATA', which contains the application data.
The administration part contains information that describes the data record in the context of the Intermediate Document (for example, the IDoc number).
The fields 'SEGNAM' and 'HLEVEL' must be filled by the parent program.
The fields 'SEGNUM' and 'PSGNUM' can be filled by the function module or can be transfered during the function module call. They are checked for consistency in this case.
With the help of an ABAP/4 Dictionary structure, the field 'SDATA' can be split up and interpreted. The documentation for these structures can be found using the program 'RSEIDOC1'.
The function module can only be called in 'CREATE' mode.
Parameters
IDENTIFIER
IDOC_CONTAINERS
Exceptions
IDENTIFIER_INVALID
IDOC_CONTAINERS_EMPTY
PARAMETER_ERROR
SEGMENT_NUMBER_NOT_SEQUENTIAL
Function Group
EDI1 -
Request Idoc : Idoc ready to be transferred to application
Hi
I am getting the above error.
I am not able to process further.
In the details tab i am getting the following errors.
1 Extraction:missing messages
2.Transfer(Idoc and tRfc):ERRORS Occured
Request Idoc : Idoc ready to be transferred to application.
3. Processing : no data
4 Process Chains: Error Occured.
All of these errors are in Red.
I have cheked in BD87 WITHTHE IDOC NO. IT shows red status with Idoc enteries in tRFC queues
I don't know how to proceed further.
Please help in this issue asap.
Thanks in advance.1) Transact RFC error
tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
queue thats under outbound processing and click on display the IDOC which is on the menu bar.
Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
(Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
to the particular TRFC request for that Idoc.
OR
Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
(For this in RSMO Screen> Environment> there is a option for Job overview.)
This Data Package TID is Transaction ID in SM58.
OR
SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
Transaction ID.
In the Status Text column you can see two status
Transation Recorded and Transaction Executing
Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
execute the "Execute LUWs"
OR
Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
EDIT ---> Execute LUW
This should help.
Also check these transactions to get more info on IDOCS.
WE02 Display IDoc
WE05 IDoc Lists
WE06 Active IDoc monitoring
WE07 IDoc statistics
WE08 Status File Interface
WE09 Search for IDoc in Database
WE10 Search for IDoc in Archive
WE23 Verification of IDoc processing
Thanks,
JituK -
IDoc ready to be transferred to application
Hello all,
I have an XI scenario that transfers a producft in MATMAS05 format to ECC, but when it arrives in the ECC system the IDoc is staying in yellow state. It says IDoc ready to be transferred to application, but it's not going for some reason. I'm sorry for the obviously newbie quesion, but does anyone have any idea as to why this may be happening?Ethan
You can go to BD87 and select option "Process it" if its in yellow state.
Best regards,
raj. -
Hello All,
Many loads failed in Production, and in the monitor status it show
Extraction (messages): Missing messages (Status :Yellow)
Missing message: Request received (Status :Yellow)
Missing message: Number of sent records (Status :Yellow)
Missing message: Selection completed (Status :Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings (Status :Yellow)
Request IDoc : IDoc ready to be transferred to application (Status :Yellow)
Processing (data packet): No data (Status :Yellow)
I went through the below who has the same issue and solved it by increasing the work process of the IDOC's. Can anybody explain how to increase the work process of the Idocs and also the reason for the failure.
Re: Issue while uploading data from R/3 production to BW productionHi Ram
I am getting the same error as you have stated here
the error is
Requests (messages): Everything OK (Status:Green)
Data request arranged (Status:Green)
Confirmed with: OK (Status:Green)
Extraction (messages): Missing messages
Data request received (Status:Green)
Missing message:No of sent records (Status:Yellow)
Missing message:Selection completed (Status:Yellow)
Transfer (IDocs and TRFC): Missing messages or warnings (Status:Green)
Request IDoc : IDoc ready to be transferred to application (Status:Green)
Info IDoc 1 : Application document posted (Status:Green)
Processing (data packet): No data
Please...... I think you cn guide me in this as u already resolved this type of error
Thanks in advance -
R/3 connection to BIW - No Idocs arrived from the source system
Question,
Hi Team,
I have issues during loading attribute data from R/3 source system to BI,
I go to the path
Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
Later I select the following options
Full Update = select
On the Processing tab page, select only PSA.
On the Schedule tab page, choose Start Data Load Immediately and start the data load.
Till here everything is in active version and saved, and connection to the source system is active and working fine.
However when I do loading I received following messages, what I observed in Monitor window,
Data was requested OK
Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
No Idocs arrived from the source system.
When I go to detail tab, under transfer section, I receive the following message
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
But when I chose to run the transformation I donu2019t get data here,
Kindly help me to resolve this issue,
Regards,
BluSKyHi,
the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
i am not sure about transactions settings about r/3 side,
could you plz throw some light on this issue,
regards
blusky -
IDoc ready to be transferred to application : Automatic Update
Hello All,
We are facing a challenge that during process chain execution, most of the request status is yellow. In most of the request there is one or more idoc which are not getting posted..and can be manually posted to BIW .
To remove the manual efforts what we thought was following ..
Schedule a background job using program RBDAPP01 and idoc status 64 (IDoc ready to be transferred to application)
Please let us know if this is the correct way to solve this problem.Any other way of doing things are welcomed.
Thanks a lot.
Regards
NimeshHi Nimesh,
Yes.This would resolve your issue.
Those IDOCs might not get posted due to non availability of dialog work process.
I hope this is the only way you can do it.
Thank you.
Regards,
Karun.M -
Status64: IDoc ready to be transferred to application
Hi,
The IDOC is coming to SAP but the status is 64 "IDoc ready to be transferred to application". Can you guys help me to process this IDOC successfully.
BR,
Madan AgrawalHi Madhan,
Fallow the steps...
1. SAP transaction code: BD64 Type /nbd64 in the SAP input window and press the
Enter key.
2. Notice that the Create model view push button is gray. This means that the function is
disabled.
3. Click the Distributional Model pull-down menu.
4. Select Switch processing mode to enable the Create model view function.
5. Click Create model view.
6. Fill in the Short text field.
7. Enter a meaningful Technical name.
8. Keep the Start date and the End date unchanged. The SAP system will prompt the
current date as the Start date. It will also prompt an end date, which is beyond most of
our lifetimes (December 31, 9999).
9. Click the green check icon to continue.
You will now see a new entry created with the short text you entered on the left side and the technical name on the right side.
10. Highlight the new entry.
11. Click Add message type on the top of the screen.
12. Fill in the information Sender as the SAP LS, Receiver as the LS of the remote system and message Type as MATMAS.
If you expand the new distribution model you will see that a new entry for the
message type MATMAS was created. If you need to support more message types, you need to repeat the Add message type operation for each of the SAP message types you will support.
The message type MATMAS will be supported for the outbound operations. SAP will send the MATMAS message type to remote LS.
If you will support inbound messages, you will need to specify Remote System LS as the sender and SAP LS as the receiver.
After you added all message types you want to support, you need to save your work:
14. Click the save icon (or press Ctrl+S) to save the model you just created.
15. You will see the message Distribution model has been saved displayed at the bottom of the SAP screen indicating that your work has been saved.
Generate a Partner Profile
A Partner Profile is defined for every SAP business partner. A partner is a remote SAP system or legacy system with which you exchange data. In our example, the partner is the remote system LS.
1. Highlight the newly created distribution entry in the SAP distribution model
screen.
2. Click the Environment pull-down menu.
3. Select Generate partner profiles.
4. In the Postprocessing:Authorized processors section of the previous screen, enter US as the user type. In partner system specify the remote LS.
5. Change the ID field if it is necessary. The fields default is the user id currently signed on to the SAP system. You may change it to the person who will be responsible for maintaining this partner profile.
6. Change the Outbound parmtrs: Output mode and Inbound parmtrs: Processing fields if it is necessary. Transfer IDoc immediately and Trigger immediately are selected as the default values,
7. Click on the execute button on the left corner of the system(resembles like a timer).
8. The return screen shown following will display. It is typical for you to receive a warning (pink/red) message such as Port could not be created". The reason for this message is you have not had an opportunity to tell SAP which port you will use for this partner profile. We will set it manually in the next step.
Modify the profile of the partner logical
system
The following steps explain how to modify the profile of the partner logical system.
1. Transaction code: WE20 Type /nwe20 on the SAP input window and press the Enter key.
2. Expand Partner Type LS (Logical System).
3. Click item remote system LS (or the name you use for the partner logical system).
4. Scroll down to see the Create outbound parameter icon +(add) below Outbound parmtrs table.
5. The Partner profiles: Outbound parameters will be displayed. Enter the following information:
Partn. funct.: Leave blank, as it is.
Message type: MATMAS
Receiver port: ALEport (or the port name you used.
Output mode: Select Transfer IDoc immed and Do not start subsystem.
IDoc Type:
o Basic Type: MATMAS03.
o Leave other fields as they are.
6. If you have more outbound parameters, repeat steps 4 and 5. If you support any inbound
parameters, perform the steps for creating inbound parameter. The steps for creating inbound parameters are similar to those for creating outbound parameters. The Create inbound parameter icon is located under the inbound params table, which is located below the outbound parameter table. If you are not sure whether you support any inbound messages, check the previous section, Create a distributional model, or use the SAP transaction code BD64 to view the distributional model.
7. Click the save icon (or press Ctrl+S) to save the outbound parameters you just created for the message type MATMAS.
8. You will see a message, Data saved displayed at the bottom of the SAP screen indicating that your work has been saved.
9. You will see that the MATMAS entry is added to the outbound parameter table.
Generating an Idoc definition file:WE61
give the basic type as matmas03 and right click on the screen you will find Parser click on that
This screen will be displayed.
now go to System-list-save-local file
We will get screen like this and here make sure that radio button is unconverted and then click on enter.
A window or pop up will be coming where in u can specify directory where the file is to be saved.
BD10 will be used for the transportation of the Idoc.
Next go to Go to bd87 and Process It.
Give u r IDOC Number there..
Hope this information is useful to you..
Thanks,
Satya Kumar..
Reward points if it is useful.. -
Idoc ready to be transferred to app
trying to run an inbound idoc pordcr101
i get status 64 idoc ready to e transferred to app
how do i transfer it???
thank youhi michal
i think my whole problem is that it is asking for purchase org
i use 3000 which is what i see in me23n when i look at old po
for doc_type is use BTW????is this for creating a po
i guess what i am lacking is a good place to see what is absolutely necessary to enter this idoc pordcr101 i look in bapi explorer it defines the fields but it does not say if they are required. also like doc_type there are no field values shown so i do not know what are actual allowed inputs for this field
there was a good source at the interface repository but it seems that link is gone
any help would be greatly appreciated -
Master IDOC but not the communication IDOC
Hi
what is master IDOC and the communication IDOC
what is the diff?
i have installed sap gui in my system and how to connect the sapserver through internet?HI SAPABAP,
1>Master idoc is only created but it won't be stored in database,where as communication idoc is stored in database.
2>Data is transferred via communication idoc not by master idoc.
Regards,
Nagaraj -
Error - Conditions in IDoc E1EDP05 have been transferred: Check data
Hi
I am procesing a ORDERS05 idoc .
in foreground the document is posted but when i run the idoc in background i get the following error.
<b>Conditions in IDoc E1EDP05 have been transferred: Check data
</b>
any idea why is such an error is occuring
Thanks
NikhilHi,
I have same problem here 'Conditions in IDoc E1EDP05 have been transferred: Check data' while transfer PO to SO.
I have tried in doing SMME, but it show me 'Client 800 has status 'not modifiable''.
What I should do the next?
Many Thanks. -
How to release the IDOC based on the count
Hi IDOC gurus,
How to release IDOC's based on the count?
Actually, my requirement is I have to release the IDOC's of count 50 for every 5 or 10 minutes. I tried by scheduling the background job for the program RSEOUT00, but unfortunately there was no option of selecting the IDOC's based on count for the given message type except IDOC range i.e FROM and TO select options in the selection screen.
Are there any other alternative where I can release the IDOC's based on count for every periodic 5 or 10minutes?
Also, can I know how can we configure the multiple QUEUES for the IDOC's?
I highly appreciate who can help regarding this and points are awarded.
Thanks,
Sreevani.Hi Ferry,
I tried with that option. Maximum number of IDocs parameter is the package size not the count of IDOC's.
I have 100 IDOC's with status 30 and all IDOC's got released eventhough the value of "Maximum number of IDocs" parameter is 50. I checked in the code it is an package size i.e., maxm IDOCs that it can be transferred from RFC outbound queue to a port at time and not maximum number that can be processed for the program execution.
Thanks,
Sreevani. -
Hi Experts,
When generating the IDOC normally we can see(read) idoc data in the idoc file.Now, i want to make this file into Encrypted format.How can i do this while generating the IDOC.
Rewared guaranteed,
thanks
kakiHI Sameena,
Can u explain me little more about ecryption of data before populating it into IDOC.
When i generate payment idoc into usr/sap path, my end user need more security.Nobody can change the data if it is in encrypted format.Could you pls explian me where to use this function modules for payment IDOCs.
SAP---->Encrypted IDOC---->BANK(here they will decrypt the data)
Maybe you are looking for
-
How to find the AK Region name from JSP
I have the requirement to hide some of the fields/regions in Oracle Sales Online. To do that from AK Developer Region Name/Code and Region Item is required. How to find this Region Code.
-
Driver for HP 2600n on Mavericks
Looking for the print driver for an HP2600n on OS X Mavericks. Ideas? The HP website only lists drivers through OS X 10.7 and says "You should get the driver from Apple"
-
Hi, Could any one tell me where I can find the Block status field in HRtables... I need to include an additional field to indicate the block status of the cost centers. Please help me asap. Regards, Charan
-
How to create updateble View Objects
Hi All, I need Help on this issue. I am using jdev 10g. Is there any Option to create Updateble VO or i need write any coding Thanks NR
-
Problem with database connectivity
Hi guys, I'm having a problem with database connectivity . I'm using the mySQL database & org.gjt.mm.mysql driver. I've kept the org folder under the directory where the Database.java program is residing . My program is as follows: import java.sql.*;