IDOCs in IS Oil

Hi,
I wanted to post the IS Oil relevant materials (with multiple units of measure) to SAP through interface. Is there any IDOC specially designed by SAP to take care of this posting?
Else please let me know what all are the different IDOCs available ipost the goods movement against process order in IS Oil.
Thanks & Regards

Hi,
For Article Master try Basic Type OILMAT03, OILMAT04, OILMAT05.
For Material Movements Try Basic Type OILMDD01
Regards
GK.
Edited by: Gnana Kumar on Nov 12, 2010 7:04 AM

Similar Messages

How To Process Inbound Shipment IDOC of IS-OIL ?

Hi Expert,
We are on 4.7E IS-OIL. We have one requirement thru which we are getting the Shipment IDOC from SCM system which is coming to R/3. The IDOC Message Type Which is Flowing From SCM To R/3 is OILSH1 & Basic Type is OILSHI01.
I want to Know how to Process this IDOC as InBound IDOC in R/3 & create the Shipment Doucment from it in R/3.
What is the Process Code & Function Module I should use.
Kindly give me the Step By Step Settings if Possible. like Partner Profile etc.
Regards,
Umesh

Hi,
Idocs Works on tRFC Queues.
Check this Report to Process Inbound Idocs with Specified Status.
RBDAPP01
Regards
Seshagiri

Steps for configuring Outbound Idoc OILSHI01

Hi experts,
 can anybody tell me the steps how to configure an Outbound IDOC.
 It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
 if not anything else will also do.
 Kindly give me steps in detailed. Since i have never done this. Including
 distribution modle (BD64). in which case it generates the Automatic Partner
 profiles.?
<REMOVED BY MODERATOR>
Regards,
Umesh
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

Hi Umesh,
Sorry for the late reply. Let me clear your couple of misconceptions first.
Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
Now the further steps:
Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
2. Again, ask your functional consultant, as to which output type is configured for your business transaction. Select that output type and go to "Processing routines".
3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc.
Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
 a. trigger the idoc on saving the doucment. this triggers idoc as soon as you save the idoc.
 b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
 c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
Hope this was helpful.
<REMOVED BY MODERATOR>
Cheers,
Karan
Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

ALEAUD to sending system in ALE scenario using XI

Hi,
I have a quite simple ALE scenario with following components;
SAP IS/OIL -> (CREMAS) -> XI -> (CREMAS) -> SAP Retail
I have read both how-to-guides; IDOC-XI scenarios and handle ack. for IDOCs.
By activating the runtime paramter ACK_SYSTEM_FAILURE, XI will send ALEAUD in case of error on XI - this works in a way.
By using program RBDSTATE on SAP Retail - this works in a way.
Challenge 1:
In case of error on XI, the ALEAUD message sent back to IS/OIL doesn't contain neither message type or the referenced IDOC from IS/OIL;
E1ADHDR-MESTYP
E1ADHDR-MESTYP_LNG
E1STATE-DOCNUM
is missing.
Anyone with ideas?
Challenge 2:
The ALEAUD from SAP Retail (using RBDSTATE) is not referring to the right IDOC from the sending system, seems to me that Retail is using it's own number range.
Anyone with ideas?
best regards
Torstein

Hi,
Even I have the same problem.
I have configured ALEAUD in Integration server. When there is an error ( sa incorect RFC Destination of Receiver), an ALEAUD message type iDoc is sent back to the sender SAP System. But i noticed that the iDoc has only data in the segment E1STATE ( with data status, statxtstamid). But the segments E1AHDHR and E1PRTOB are empty.
The acknowledgement idoc doesnt contain any reference to the message( like the message ID) which has gone for an error. It just contains error text.
Could you please let me know how you solved it
Thanks & Regards,
Vani

Creation of IS OIL TD Shipment using Inbound IDOC Processing?

HI Expert,
We are on IS OIL 4.72E version . As part of once of our requirement we need to process inbound shipment IDOC from SCM system and create the TD Shipment document in R/3 ..
Delivery is already created in R/3 ; In SCM assginement of vehicle is done and IDOC is transferred to R/3.
I want to know how to process this inbound shipment IDOC ; for creating only TD shipment not the delivery as it is already exist.. what is the process code and function module to be given in partner profile....
Kindly explain me step by step if possible....
Regards,
Adityakumar Waghmode

Hi,
Function module field is used to define the path functionality of file generated.
EDI_PATH_CREATE_CLIENT_DOCNUM is the recommned fucntion by SAP .
Function is used to prevent unprocessed files being overwritten.Tihs function generates file directory path dynamically.
Hope this helps.
Thanks.
Mark points if helpful.

LiveCache for SAP HCM Idocs ECC6EHP4 on windows/mssql

Hello Gurus,
We am trying to process inbound HR Idoc (message type HRMD_A) from a java system and during the process it stucks in error code 51 and error message says - "Unable to establish connection to LiveCache".
Now we dont have any Livecache setup here but we built the system based upon a system copy and i can see some LiveCache system maintained there in tcode DB59 and DBACOCKPIT but we dont have those systems in our landscape as the system copy was from SAP originally.
Now the question is Do we need LiveCache for SAP HR HCM module specifically to proess HR Idocs (inbound only, outbound process works fine).
I read a lot of stufff on live cache technology but i think that is required only for SAP SCM(Supply chain management).
If i need to install livecache what would be the ideal steps, currently my ECC EHP4 system is on windows 2003 server/ MSSQL 2005.
Do i need to install MAXDB along with MSSQL to support livecache as its only supported on MaxDB(correct me if i am wrong).
Any reply will be highly appreciated.
Mani

Hello Natalia,
Thank you for your reply, but we want to resolve it if possible without SAP support
please find my answers below for your uestion
-> Is your system connected to CRM system?
No
-> Is your system connected to SCM system?
No
-> What connections you saw in /ndb59 on your system?
To a unknown SAP SID which is in red color, that means not active.
-> What SAP components, with SP number, installed on your system?
WE have basically SAP ERP with SAP HR as the main component we are working on this system.
following is the full list of component
S/w component     Release     Level     Highest support Package     S/w Description
SAP_ABA     701     4     SAPKA70104     Cross-Application Component
SAP_BASIS     701     4     SAPKB70104     SAP Basis Component
PI_BASIS     701     4     SAPK-70104INPIBASIS     Basis Plug-In
ST-PI     2008_1_700     0          -     SAP Solution Tools Plug-In
SAP_BS_FND     701     1     SAPK-70101INSAPBSFND     SAP Business Suite Foundation
SAP_BW     701     2     SAPKW70102     SAP Business Warehouse
LCAPPS     2005_700     5     SAPKIBHD05     LC Applications (LCAPPS) 2005_700
SAP_AP     700     14     SAPKNA7014     SAP Application Platform
WEBCUIF     700     1     SAPK-70001INWEBCUIF     SAP WEBCUIF 700
SAP_APPL     604     1     SAPKH60401     Logistics and Accounting
SAP_HR     604     4     SAPKE60404     Human Resources
SAP_HRCAR     604     4     SAPK-60404INSAPHRCAR     Sub component SAP_HRCAR of SAP_HR
SAP_HRCAT     604     4     SAPK-60404INSAPHRCAT     Sub component SAP_HRCAT of SAP_HR
SAP_HRCAU     604     4     SAPK-60404INSAPHRCAU     Sub component SAP_HRCAU of SAP_HR
SAP_HRCBE     604     4     SAPK-60404INSAPHRCBE     Sub component SAP_HRCBE of SAP_HR
SAP_HRCBR     604     4     SAPK-60404INSAPHRCBR     Sub component SAP_HRCBR of SAP_HR
SAP_HRCCA     604     4     SAPK-60404INSAPHRCCA     Sub component SAP_HRCCA of SAP_HR
SAP_HRCCH     604     4     SAPK-60404INSAPHRCCH     Sub component SAP_HRCCH of SAP_HR
SAP_HRCCL     604     4     SAPK-60404INSAPHRCCL     Sub component SAP_HRCCL of SAP_HR
SAP_HRCCN     604     4     SAPK-60404INSAPHRCCN     Sub component SAP_HRCCN of SAP_HR
SAP_HRCDE     604     4     SAPK-60404INSAPHRCDE     Sub component SAP_HRCDE of SAP_HR
SAP_HRCDK     604     4     SAPK-60404INSAPHRCDK     Sub component SAP_HRCDK of SAP_HR
SAP_HRCES     604     4     SAPK-60404INSAPHRCES     Sub component SAP_HRCES of SAP_HR
SAP_HRCFI     604     4     SAPK-60404INSAPHRCFI     Sub component SAP_HRCFI of SAP_HR
SAP_HRCFR     604     4     SAPK-60404INSAPHRCFR     Sub component SAP_HRCFR of SAP_HR
SAP_HRCGB     604     4     SAPK-60404INSAPHRCGB     Sub component SAP_HRCGB of SAP_HR
SAP_HRCHK     604     4     SAPK-60404INSAPHRCHK     Sub component SAP_HRCHK of SAP_HR
SAP_HRCID     604     4     SAPK-60404INSAPHRCID     Sub component SAP_HRCID of SAP_HR
SAP_HRCIE     604     4     SAPK-60404INSAPHRCIE     Sub component SAP_HRCIE of SAP_HR
SAP_HRCIN     604     4     SAPK-60404INSAPHRCIN     Sub component SAP_HRCIN of SAP_HR
SAP_HRCIT     604     4     SAPK-60404INSAPHRCIT     Sub component SAP_HRCIT of SAP_HR
SAP_HRCJP     604     4     SAPK-60404INSAPHRCJP     Sub component SAP_HRCJP of SAP_HR
SAP_HRCKR     604     4     SAPK-60404INSAPHRCKR     Sub component SAP_HRCKR of SAP_HR
SAP_HRCMX     604     4     SAPK-60404INSAPHRCMX     Sub component SAP_HRCMX of SAP_HR
SAP_HRCMY     604     4     SAPK-60404INSAPHRCMY     Sub component SAP_HRCMY of SAP_HR
SAP_HRCNL     604     4     SAPK-60404INSAPHRCNL     Sub component SAP_HRCNL of SAP_HR
SAP_HRCNO     604     4     SAPK-60404INSAPHRCNO     Sub component SAP_HRCNO of SAP_HR
SAP_HRCNZ     604     4     SAPK-60404INSAPHRCNZ     Sub component SAP_HRCNZ of SAP_HR
SAP_HRCPH     604     4     SAPK-60404INSAPHRCPH     Sub component SAP_HRCPH of SAP_HR
SAP_HRCPT     604     4     SAPK-60404INSAPHRCPT     Sub component SAP_HRCPT of SAP_HR
SAP_HRCRU     604     4     SAPK-60404INSAPHRCRU     Sub component SAP_HRCRU of SAP_HR
SAP_HRCSE     604     4     SAPK-60404INSAPHRCSE     Sub component SAP_HRCSE of SAP_HR
SAP_HRCSG     604     4     SAPK-60404INSAPHRCSG     Sub component SAP_HRCSG of SAP_HR
SAP_HRCTH     604     4     SAPK-60404INSAPHRCTH     Sub component SAP_HRCTH of SAP_HR
SAP_HRCTW     604     4     SAPK-60404INSAPHRCTW     Sub component SAP_HRCTW of SAP_HR
SAP_HRCUS     604     4     SAPK-60404INSAPHRCUS     Sub component SAP_HRCUS of SAP_HR
SAP_HRCVE     604     4     SAPK-60404INSAPHRCVE     Sub component SAP_HRCVE of SAP_HR
SAP_HRCZA     604     4     SAPK-60404INSAPHRCZA     Sub component SAP_HRCZA of SAP_HR
SAP_HRGXX     604     4     SAPK-60404INSAPHRGXX     Sub component SAP_HRGXX of SAP_HR
SAP_HRRXX     604     4     SAPK-60404INSAPHRRXX     Sub component SAP_HRRXX of SAP_HR
EA-IPPE     404     1     SAPK-40401INEAIPPE     SAP iPPE
EA-APPL     604     1     SAPK-60401INEAAPPL     SAP Enterprise Extension PLM, SCM, Finan
EA-DFPS     604     1     SAPK-60401INEADFPS     SAP Enterprise Extension Defense Forces
EA-FINSERV     604     1     SAPK-60401INEAFINSRV     SAP Enterprise Extension Financial Servi
EA-GLTRADE     604     1     SAPK-60401INEAGLTRAD     SAP Enterprise Extension Global Trade
EA-HR     604     4     SAPK-60404INEAHR     SAP Enterprise Extension HR
EA-HRCAR     604     4     SAPK-60404INEAHRCAR     Sub component EA-HRCAR of EA-HR
EA-HRCAT     604     4     SAPK-60404INEAHRCAT     Sub component EA-HRCAT of EA-HR
EA-HRCAU     604     4     SAPK-60404INEAHRCAU     Sub component EA-HRCAU of EA-HR
EA-HRCBE     604     4     SAPK-60404INEAHRCBE     Sub component EA-HRCBE of EA-HR
EA-HRCBR     604     4     SAPK-60404INEAHRCBR     Sub component EA-HRCBR of EA-HR
EA-HRCCA     604     4     SAPK-60404INEAHRCCA     Sub component EA-HRCCA of EA-HR
EA-HRCCH     604     4     SAPK-60404INEAHRCCH     Sub component EA-HRCCH of EA-HR
EA-HRCCN     604     4     SAPK-60404INEAHRCCN     Sub component EA-HRCCN of EA-HR
EA-HRCDE     604     4     SAPK-60404INEAHRCDE     Sub component EA-HRCDE of EA-HR
EA-HRCDK     604     4     SAPK-60404INEAHRCDK     Sub component EA-HRCDK of EA-HR
EA-HRCES     604     4     SAPK-60404INEAHRCES     Sub component EA-HRCES of EA-HR
EA-HRCFI     604     4     SAPK-60404INEAHRCFI     Sub component EA-HRCFI of EA-HR
EA-HRCFR     604     4     SAPK-60404INEAHRCFR     Sub component EA-HRCFR of EA-HR
EA-HRCGB     604     4     SAPK-60404INEAHRCGB     Sub component EA-HRCGB of EA-HR
EA-HRCHK     604     4     SAPK-60404INEAHRCHK     Sub component EA-HRCHK of EA-HR
EA-HRCID     604     4     SAPK-60404INEAHRCID     Sub component EA-HRCID of EA-HR
EA-HRCIE     604     4     SAPK-60404INEAHRCIE     Sub component EA-HRCIE of EA-HR
EA-HRCIN     604     4     SAPK-60404INEAHRCIN     Sub component EA-HRCIN of EA-HR
EA-HRCIT     604     4     SAPK-60404INEAHRCIT     Sub component EA-HRCIT of EA-HR
EA-HRCJP     604     4     SAPK-60404INEAHRCJP     Sub component EA-HRCJP of EA-HR
EA-HRCKR     604     4     SAPK-60404INEAHRCKR     Sub component EA-HRCKR of EA-HR
EA-HRCMX     604     4     SAPK-60404INEAHRCMX     Sub component EA-HRCMX of EA-HR
EA-HRCMY     604     4     SAPK-60404INEAHRCMY     Sub component EA-HRCMY of EA-HR
EA-HRCNL     604     4     SAPK-60404INEAHRCNL     Sub component EA-HRCNL of EA-HR
EA-HRCNO     604     4     SAPK-60404INEAHRCNO     Sub component EA-HRCNO of EA-HR
EA-HRCNZ     604     4     SAPK-60404INEAHRCNZ     Sub component EA-HRCNZ of EA-HR
EA-HRCPH     604     4     SAPK-60404INEAHRCPH     Sub component EA-HRCPH of EA-HR
EA-HRCPT     604     4     SAPK-60404INEAHRCPT     Sub component EA-HRCPT of EA-HR
EA-HRCRU     604     4     SAPK-60404INEAHRCRU     Sub component EA-HRCRU of EA-HR
EA-HRCSE     604     4     SAPK-60404INEAHRCSE     Sub component EA-HRCSE of EA-HR
EA-HRCSG     604     4     SAPK-60404INEAHRCSG     Sub component EA-HRCSG of EA-HR
EA-HRCTH     604     4     SAPK-60404INEAHRCTH     Sub component EA-HRCTH of EA-HR
EA-HRCTW     604     4     SAPK-60404INEAHRCTW     Sub component EA-HRCTW of EA-HR
EA-HRCUS     604     4     SAPK-60404INEAHRCUS     Sub component EA-HRCUS of EA-HR
EA-HRCVE     604     4     SAPK-60404INEAHRCVE     Sub component EA-HRCVE of EA-HR
EA-HRCZA     604     4     SAPK-60404INEAHRCZA     Sub component EA-HRCZA of EA-HR
EA-HRGXX     604     4     SAPK-60404INEAHRGXX     Sub component EA-HRGXX of EA-HR
EA-HRRXX     604     4     SAPK-60404INEAHRRXX     Sub component EA-HRRXX of EA-HR
EA-PS     604     1     SAPK-60401INEAPS     SAP Enterprise Extension Public Services
EA-RETAIL     604     1     SAPK-60401INEARETAIL     SAP Enterprise Extension Retail
FINBASIS     604     1     SAPK-60401INFINBASIS     FINBASIS
C-CEE     110_604     0          -     ECC Core Country Versions for EEM Countr
CPRXRPM     450_700     4     SAPK-45004INCPRXRPM     SAP xRPM/cProjects/cFolders 4.50 (ABAP)
ECC-DIMP     604     1     SAPK-60401INECCDIMP     DIMP
ECC-SE     604     1     SAPK-60401INECCSE     ESA FAST TRACK (ERP) 2005
ERECRUIT     604     1     SAPK-60401INERECRUIT     ERECRUIT
FI-CA     604     1     SAPK-60401INFICA     FI-CA
FI-CAX     604     1     SAPK-60401INFICAX     FI-CA Extended
HR-CEE     110_604     0          -     HR country version for CEE countries
HR-CEECBG     110_604     0          -     Sub component HR-CEECBG of HR-CEE
HR-CEECCO     110_604     0          -     Sub component HR-CEECCO of HR-CEE
HR-CEECCZ     110_604     0          -     Sub component HR-CEECCZ of HR-CEE
HR-CEECHR     110_604     0          -     Sub component HR-CEECHR of HR-CEE
HR-CEECHU     110_604     0          -     Sub component HR-CEECHU of HR-CEE
HR-CEECPL     110_604     0          -     Sub component HR-CEECPL of HR-CEE
HR-CEECRO     110_604     0          -     Sub component HR-CEECRO of HR-CEE
HR-CEECSI     110_604     0          -     Sub component HR-CEECSI of HR-CEE
HR-CEECSK     110_604     0          -     Sub component HR-CEECSK of HR-CEE
HR-CEECTR     110_604     0          -     Sub component HR-CEECTR of HR-CEE
HR-CEECUA     110_604     0          -     Sub component HR-CEECUA of HR-CEE
HR-CEEGXX     110_604     0          -     Sub component HR-CEEGXX of HR-CEE
HR-CEERXX     110_604     0          -     Sub component HR-CEERXX of HR-CEE
INSURANCE     604     1     SAPK-60401ININSURANC     SAP Insurance
IS-CWM     604     1     SAPK-60401INISCWM     Industry Solution Catch Weight Managemen
IS-H     604     1     SAPK-60401INISH     SAP Healthcare
IS-M     604     1     SAPK-60401INISM     SAP MEDIA
IS-OIL     604     1     SAPK-60401INISOIL     IS-OIL
IS-PRA     604     1     SAPK-60401INISPRA     SAP IS-PRA
IS-PS-CA     604     1     SAPK-60401INISPSCA     IS-PS-CA 604 Upgrade
IS-UT     604     1     SAPK-60401INISUT     SAP Utilities/Telecommunication
LSOFE     604     1     SAPK-60401INLSOFE     LSOFE
PLMWUI     700     1     SAPK-70001INPLMWUI     SAP PLM Web UI
RTLWFM     100     3     SAPK-10003INRTLWFM     RTLWFM 100: Add-On Installation
SEM-BW     604     1     SAPK-60401INSEMBW     SEM-BW
SLL-LEG     720     1     SAPK-72001INSAPSLL     SLL-LEG 720 : Add-On Installation
SLL_PI     720_603     1     SAPK-72901INSLLPI     GTS Plug-In
WFMCORE     200     11     SAPK-20011INWFMCORE     WFMCORE 200 Upgrade: Meta-Commandfile (D
GRC_RM_ABP     200     11     SAPK-20011INGRCRMABP     GRC_RM_ABP 200: Add-On Installation
AIN     400     2     SAPK-40002INAIN     AIN 400 : Add-On Supplement
AOFTOOLS     400_700     0          -     Add-On Assembly Kit (AOFTOOLS 400_700)
GRCPCRTA     250_700     5     SAPK-25605INGRCPCRTA     GRCPC 250 RTA for 700
GRCSPC     250     5     SAPK-25005INGRCSPC     GRC Process Control 250
MRSS     610     3     SAPK-61003INMRSS     Multi Resource Service Scheduling
ST-A/PI     01L_ECC600     0          -     Application Servicetools for ECC 600
TDAGBCA     110_600     2     SAPK-26002INTDAGBCA     TechniData Basic Components
VIRSAHR     530_700     3     SAPK-53303INVIRSAHR     SAP GRC Access Controls 5.3 for 700 HR S
VIRSANH     530_700     4     SAPK-53304INVIRSANH     SAP GRC Access Controls 5.3 for 700 HR a
XFT     240_700     0          -     xft business add-on
Thanks
Mani

IS-OIL - Invalid ROLLBACK WORK in an update function module

Hi,
I am getting this dump which points to CL_PO_HEADER_HANDLE_MM========CP.
In the system Update Records (SM13) there is an error for transaction O4NM for custom function ZOIJ_UPDATE_RELATED_DOCS.
I have no experience with OIL module so any advice on how to go about tracing the cause of this error would be appreciated.
Regards,
Warren.

Hi Christian,
I am not sure how the update is being done. Am trying to hold of the documents that caused the error so that I can replicate it.
You are correct, the dump only occurs occassionally and not every time.
I have tried to find the sales doc number but unfortunately this is not in the dump.
I did a where used list on the function and found one where it is called in update task which I think is where it is falling over:
CODE:
in cases where the nomination update is called
from a CT contract, sales order etc
we dont want to update the related document
or it will cause locking issues and
circular reference
flag can be set in BAPI header
Further to this
there are cases where there are many nomination Idocs
entering the system,
the nomination update calls the
OIJU_RD_UPDATE_OBJ_ENTRIES function
the related document update calls the same function
this is normally not a problem as the V2 update will
not intefere with the normal V1 update
but in the case of multiple nomiantions, even when called
synchronously, the V2 update from the first related doc\
update is causing issues with the secon nomination V1 update
deadlocks ensue
therefore - setting the flag to '1' in the BAPI header will e
ensure the related document update is called in the same task
in cases = '1' the update is called from validation
routine in order for message handling
 CASE is_nom_header-zz_no_rel_upd.
 WHEN space.
**>>> lock CT contracts to be updated in update task "SD1K952062
**--- exported in method DATABASE_UPDATE_PREPROCESSING
 import ZOIJ_EVENT to ct_nom_event from memory id 'ZOIJCTLOCK'
 delete ct_nom_event
 where cre_name eq space
 and updkz eq space.
**>>> field changes which also need to be updated
 into the related document (STO/PO/SO) will be
 updted into CT via the related doc i.e.
 BAPI update to STO/PO/SO
 other changes i.e. the event dates are updated
 directly from NOMI into the CT contract
 for those cases we need to lock the CT contract
 here
**>>> check how the CT contract needs to be updated
 Nothing changed = from NOMI directly
 Data changed = via related document
 call function 'ZOIJ_CHECK_DATA_CHANGED'
 EXPORTING nomtk = is_nom_header-nomtk
 i_nomh = is_cd_oijnomh_new
 i_nomi = lt_nomi
 CHANGING chg_flag = chg_flag
 EXCEPTIONS nothing_changed = 4
 data_changed = 8
 others = 12.
 if sy-subrc eq 4 and
 chg_flag is initial.
**--- direct update from NOMI if event dates have changed
 check if such changes and lock the CT contract
 call function 'ZOIJ_LOCK_RELATED_CONTRACTS'
 tables it_oijnomi = lt_nomi
 it_oijne = ct_nom_event.
 endif.
**<<< end
 CALL FUNCTION 'ZOIJ_UPDATE_RELATED_DOCS' IN UPDATE TASK
 EXPORTING
 nomtk = is_nom_header-nomtk
 mem_tab = mem_tab
 i_nomh = is_cd_oijnomh_new
 i_nomi = lt_nomi
 TABLES
 it_oijne = lt_oijne
 EXCEPTIONS
 error = 1
 OTHERS = 2.

How to Find Out whether Standard IDOC is Availabl for Transaction ?

Hi,
    We are having SAP implementation 4.7E IS-OIL. We would like to know how to find out whether is there any Standard IDOC is Available for the SAP Transaction.
Particularly for IS-Oil related transaction. e.g Load Confiramtion. T-code - O4G1.
    From a Given Transaction code is there any link which can tell whether IDOC is Present or not.
     Kindly help me.
Regards,
Umesh

check for transaction....we41 and we42..
check for proper process code...then check in we57,we81 and we82..
also u can search in google..
UMESH note that u need some fucntional exp for working in IDOC...try to crack yr head ..give time..n u ll get to know the things soon..as there is no defined standards to work in idocs..
for more info u can ask me for [email protected]
best regards
Message was edited by:
        Madan Gopal Sharma

How to assign values to extended segments in an IDoc Orders05.

Hi All,
I am working for an oil industry client. I have a requirement to develop a Sales order interface (I am using basic type ORDERS05). After analysing the segments and fields of this basic type, I understood I need to 2 extra custom segments (for IS oil specific fields like 'CONTACT PERSON), 'Billing block' and 'Created by' fields in HEADER & 'Excise Duty Handling type', validation type in ITEM level).
<each segment for a Header and a Item>
I have extended the IDoc. But I am unaware how to fill up these custom segments. I understand there are exits in 'IDOC_INPUT_ORDERS'.
Please suggest me the steps to be considered in the exits.
Appreciate the <removed by moderator> response.
Thanks and Regards,
Kbip
Edited by: Thomas Zloch on Nov 1, 2011 10:18 AM

Hi,
Yes I tried this option. But I have come across this error 'No batch input data for screen SAPMV45A 8001'. This must be because the values are fed in wrong screen fields. But When I cross-checked the internal table BDC_DATA in the program before CALL TRANSACTION and the recording in SHDB separately, the screen numbers are different. I am wondering how to find the exact fields which is to be filled up.
Note: I am creating Sales Order with reference to a Contract. Do we need to do any special treatment for this?
Thanks

IS-OIL Downstream Customizing

Hello Experts,
I need to transfer transaction data between SAP R/3 and external system (TAS)
TAS needs following iDocs related to IS-OIL TD functionalities to handle the inbound and outbound delivery/shipment:
OILORD02
OILSHL01
OILLDD01
SISINV01
where can I find a detailed step-by-step guide on configuring TAS interface for Downstream Oil & Gas.
Thanks in Advance.

Dear Abbas,
First of all you need to decide in which sub module of SAP IS Oil you want to learn. Broadly I can say Upstream and downstream are the options. For module info please refer link:
Sub Modules in IS Oil & Gas, upstream and downstream
These are few certification available:
IOG100 – Primary & Secondary Distribution with SAP Oil & GasEHP6 ( v097 – Col97 )
IOG150 – Oil & Gas Industry Supply ChainIOG320 – Oil & Gas Exchanges Business
IOG330 – Bulk Transportation and Shipment Costing
IOG340 - Trading & Scheduling with SAP for Oil & Gas – EHP6 ( v097 – Col97 )
IOG350 – Service Station Retailing
IOGW40 – Joint Venture Accounting (JVA)

Connection between IS-Oil and IS-Banking

i need some help on what to do to communicate between IS-Oil and IS-Banking. my data is in is-oil and i need it to do a transaction in is-banking if i can use rfc what set up do i need to do to make it work or there are others that i can do. i appreciate your help thanks in advance.

You can have the communication between the two systems either by using RFC's or IDOC's. For both, you will have to create a RFC destination in SM59 transaction, usually done by the BASIS consultants.
Once that is done you call a remote enabled function from the other system, while specifying the destination of the function, which is the name of the RFC dest, that you created in SM59.
For IDOC scenarios, take a look at this blog.
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
Regards,
Ravi
Note : Please mark all the helpful answers

IDoc GOODSMOVEMENTOIL_CREATEFROMD01

Hi all,
I have a problem to import IDoc GOODSMOVEMENTOIL_CREATEFROMD01 from SAP IS-OIL (606), Add-On OGSD (610) into SAP PI. In WE30 I can see that this IDoc consists of these segment types:
E1GOODSMOVEMENTOIL_CREATEFR => doesn't exist
    E1BPOIL2017_GM_HEAD_CREATE => doesn't exist
    E1BP2017_GM_CODE
    E1BPOIL2017_GM_ITM_CRTE_01 => doesn't exist
        E1BPOIL2017_GM_ITM_CRTE_011 => doesn't exist
    E1BPOIL2017_GM_ITM_CRTE_02 => doesn't exist
    E1BPOIL2017_GM_ITM_CRTE_PAR => doesn't exist
        E1BPOIL2017_GM_ITM_CRTE_PA1 => doesn't exist
    E1BPOIL2017_GM_ITM_CRTE_QUA => doesn't exist
    E1BP2017_GM_SERIALNUMBER
    E1BPPAREX
The most of these segment types do not exist. Did the installation of Add-On OGSD failed?

Hello,
I encountered the same problem. If you are sure to have configure correctly your IDX2 transaction, be sure you have import the idoc in the repository under the good composant.
For example if IDOC is for R/3 4.6, import your idoc under SAP APPL 4.6C or SAP BASIS 4.6C to use it in the directory with a component that you defined before in your SLD as a SAP R/3 product.
Regards,
Chris

Data Collation Idoc

Hello Experts,
I am trying to create Data collation report using a standard message type '/ICO/DCDOC'. The Idoc is getting created successfully but it remains in Status '62' and it is not processing further. Can anyone help me on this?
Also if anybody has some documentation on SAP IS OIL interface related documentation please forward it to me
Thanks in advance
Ashish Jain

Hi Thorstan,
Thanks for the help. Idoc are getting posted with Status Message '53: Import document 0000000033 successfully posted" and the interface log is coming as
Interface Log
       File: 0000000033 Ref.: 0000000000202015 DCDOC01 16.05.2011 10:48:52 C512347
       File: 0000000033 Ref.: 0000000000202015 DCDOC01 16.05.2011 12:23:16 C512347
       File: 0000000033 Ref.: 0000000000202015 DCDOC01 23.05.2011 11:07:24 C512347
FA01 FA: Create Data Collation
FA02 FA: Edit Data Collation
FA03 FA: Post Data Collation
SR01 SR: Create Data Collation
SR02 SR: Edit Data Collation
SR03 SR: Post Data Collation
Now when i am trying to see this data collation report i am not able to see this. The transaction code that i am using for posting interface report is '/ICO/MO_I9'. please note that it comes under 'Old interface Node' of OGSD.
If you any documentation with you please forward it to me
Thanks for the help
Ashish Jain

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

IDoc not received in MII

Hi All,
I am using SAP MII 12.1.5 Build 87.
I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII.
We are able to send iDoc from SAP but we are not able to receive same in MII.
Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83.
Following are the log details for SAP MII Logger as well as SAP NW Log.
SAP NW Log:
Error processing JRA IDOC message
SAP MII Log:
Error processing JRA IDOC message
Error processing JRA IDOC message [server=xxx, client=xxx]
[EXCEPTION]
java.lang.NullPointerException
at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
at $Proxy943.onMessage(Unknown Source)
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Please help me out on this issue.
Regards,
Manoj Bilthare
Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

Hi Manoj,
Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
If this doesn't help you,please try restarting your server again.
How about the credential editor have you configured this as well?
Regards,
Sudhir Kumar
Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

IDOCs in IS Oil

Similar Messages

Maybe you are looking for