SHIPPING EXECUTION에 대해 DEBUG FILE을 생성하는 방법

제품: Applications
작성날짜 : 2006-05-30
SHIPPING EXECUTION에 대해 DEBUG FILE을 생성하는 방법
==========================================
PURPOSE
Shipping Execution에 대해 Debug file을 생성하는 방법을 기술함.
Explanation
Log file을 생성하기 위한 여러 방법들이 있으며, 이는 다음과 같은 patch level에 의해 결정된다.
A. debug file from the Shipping Transaction or Quick Ship forms in
version 11.5.9 or higher.
B. debug file for Pick Release in version 11.5.9 (Family pack I)
or higher.
C. debug file for Pick Release prior to version 11.5.9
D. debug file for Interface Trip Stop - SRS in version 11.5.9
(Family pack I) or higher.
E. debug file for Interface Trip Stop - SRS prior to version
11.5.9 (Family pack I).
F. debug file for an API in version 11.5.9 (Family pack I) or higher:
G. debug file for an API prior version 11.5.9 (Family pack I):
A. To generate a debug file from the Shipping Transaction or
Quick Ship forms in version 11.5.9 (Family pack I) or higher:
1. Set the following profile options:
OM: Debug Level - set to 5
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
WSH: Debug Log Directory - any directory that can be written to by
the database
여기서, 설정하는 directory는 다음을 check하여야 합니다.
To check, run the following SQL statement:
Code:
select value from v$parameter
where name = 'utl_file_dir'
Set profile option WSH: Debug Log Directory at the Site
& Application Level.
2. Shipping form --> Tools
Debug box를 check. ==> This will print out a file name
- NOTE down this file name.
3. Perform the action you wish to debug.
4. Tools --> uncheck Debug box.
5. After you have completed generating the debug file,
set profile OM: Debug Level back to 0
WSH: Debug Enabled set to No
6. step 1의 debug directory밑에 debug file이 생성됨.
B. To generate debug information for Pick Release in version 11.5.9 or
higher:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
2. Release Sales Order for Picking form --> Tools
==>check the Debug box.
3. Submit the pick release.
4. Provide "Pick Selection List Generation" log file.
C. To generate debug for Pick Release prior to version 11.5.9 :
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
2. Release Sales Order for Picking form --> Tools
==>check the Debug box.
3. Submit the pick release.
4. Provide "Pick Selection List Generation" log file.
D. To generate debug for Interface Trip Stop - SRS in 11.5.9 or higher:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
Set the Debug Level parameter to 1 (Debugging ON) .
2. Submit the job.
3. Provide the log file.
E. To generate debug for Interface Trip Stop - SRS prior to 11.5.9:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
Set the Debug Level parameter to 1 (Debugging ON) .
2. Submit the job.
3. Provide the log file.
F. To generate debug for an API in 11.5.9 or higher:
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
WSH: Debug Enabled - set to Yes
WSH: Debug Level - set to Statement
WSH: Debug Log Directory - set to a valid writeable directory path
2. Add the following line of code in the wrapper script which calls
the API:
Code:
DECLARE
l_file_name VARCHAR2(32767);
l_return_status VARCHAR2(32767);
l_msg_data VARCHAR2(32767);
l_msg_count NUMBER;
BEGIN
fnd_profile.put('WSH_DEBUG_MODULE','%');
fnd_profile.put('WSH_DEBUG_LEVEL',WSH_DEBUG_SV.C_STMT_LEVEL);
wsh_debug_sv.start_debugger
(l_file_name,l_return_status,l_msg_data,l_msg_count);
3. Submit the job.
4. Provide the log file.
G. To generate debug for an API prior to 11.5.9 (Family pack I):
1. Set the following profile options:
OM: Debug Level - set to 5
INV: Debug Level - set to 10
2. Add the following line of code in the wrapper script which calls
the API:
Code:
oe_debug_pub.initialize;
oe_debug_pub.SetDebugLevel(5);
DBMS_OUTPUT.PUT_LINE('Debug File = '
||OE_DEBUG_PUB.G_DIR||'/'||OE_DEBUG_PUB.G_FILE);
3. Submit the job.
4. Provide the log file.
Example
Reference Documents
Note#290432.1

Similar Messages

  • How do I find the program that is creating a debug file

    Hi,
    I have a bunch of debug files in /usr/tmp directory on a Unix box. I am using Oracle Apps 11i. How do I find which program is causing this file?
    There content of the debug files does not have much information to point to any particular program.
    Thanks
    Asgar

    Thanks for the update.
    The user is oracle and group is dba. I know from the name of the file that it is coming from oracle apps (somewhere in a custom program).
    Asgar

  • ESYU: R12 - R12 Trace/Debug file을 생성하는 방법

    Purpose
    Version: 12.0
    Information in this document applies to any platform.
    R12에서 Trace와 Debug file 생성 방법을 알아본다.
    Solution
    1. Navigate Responsibility: System Administrator> Profile> System>Query
    User: Trace를 생성할 user 명을 입력
    Profile: Initialization SQL Statement - Custom
    2. User columne에 아래의 내용을 입력
    begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS='||''''||'10046 TRACE NAME CONTEXT FOREVER,LEVEL 12'||''''); end;
    3. 입력한 내용을 저장
    FND debug messages를 생성:
    4. Navigate Responsibility: System Administrator> Profile> System>Query
    User: Debug를 생성할 user 명을 입력
    Profile: FND:%Debug%
    5. 아래 profile options 값을 user level로 set
    FND: Debug Log Enabled Yes
    FND: Debug Log Filename <empty>
    FND: Debug Log Level STATEMENT
    FND: Debug Log Mode Asynchronous with Cross-Tier Sequencing
    FND: Debug Log Module %
    6. 입력한 내용을 저장
    Example:
    7. Navigate: Payables Responsibility> Other> Request> Run> Select and Submit the Report
    (특정 Report를 실행한다)
    8. Trace 와 FND Debug messages를 disable
    9. FND Debug message를 찾기위해 아래 query를 실행
    select log_sequence, timestamp, module,message_text
    from fnd_log_messages fnd
    where trunc(timestamp) = trunc(sysdate)
    and (module like '%xla.%' or module like '%ap.%')
    and trunc(timestamp) = trunc(sysdate)
    order by timestamp;
    SELECT log_sequence, message_text,substr(module,1,100)
    FROM fnd_log_messages msg
    , fnd_log_transaction_context tcon
    WHERE msg.TRANSACTION_CONTEXT_ID = tcon.TRANSACTION_CONTEXT_ID
    AND tcon.TRANSACTION_ID= /*Give the request id of accounting program*/
    ORDER BY LOG_SEQUENCE desc
    Debugging의 활성화를 위해 아래 profile option을 사용:
    FND: Debug Log Enabled : Yes
    FND: Debug Log Level : Statement
    Debug message를 얻기 위해 아래 query 문을 사용:
    SELECT substr(module,1,70), MESSAGE_TEXT, timestamp, log_sequence
    FROM fnd_log_messages msg, fnd_log_transaction_context tcon
    WHERE msg.TRANSACTION_CONTEXT_ID = tcon.TRANSACTION_CONTEXT_ID
    AND tcon.TRANSACTION_ID = <your child request ID>
    ORDER BY LOG_SEQUENCE
    10. 아래 SQL을 이용해 trace file이 생성되는 위치를 확인, raw trace와 tkprof'd trace
    file을 upload
    select value
    from v$parameter
    where name = 'user_dump_dest';
    Reference
    Note 458371.1

  • Adobe plugin creates junk debug files: 'C:\\nppdf32Log\\debuglog.txt'

    Hello,
    latest Adobe Reader for Linux (9.5.5) - its plugin for firefox named nppdf32.so creates junk debug files named: 'C:\\nppdf32Log\\debuglog.txt' in directories from where a firefox was executed.
    This happens since Acrobat Reader 9.5.1 release.
    How to make Adobe fixing this bug?
    How to contact them efficiently?
    This bug exists since 9.5.1 dated 04/09/2012 and Adobe do not care. Fix is trivial for Adobe: disable debug logging in release versions and stop using Windows path 'C:\\nppdf32Log\\debuglog.txt' in Linux products.
    Workaround for this bug is trivial: open in hex editor: nppdf32.so file installed by Adobe Reader, go to position 0x0002193a in this file (or simply search for C:\ - there is only one place), and replace string:
    C:\\nppdf32Log\\debuglog.txt
    with:
    /dev/null
    Because string /dev/null is shorter than C:\\nppdf32Log\\debuglog.txt fill remainings of previous string with hex zeroes: 00 to keep everything in place.
    Come on Adobe what's wrong with you! Why you do not provide such simple fix by yourself! It's 3 minutes of primitive work!

    Here are few solutions:
    1. You can configure firefox to open pdf in external application like acroread. This way plugin problem is bypassed. - I use it this way. It looks to be faster this way.
    2. "C:\nppdf32Log\debuglog.txt" is created every time in directory from where you executed firefox/opera/other browser and opened any pdf file in browser. So this is not only home directory. You can fix this problem by yourself by hex editing nppdf.so file and replacing C:\nppdf32Log\debuglog.txt path in this file with /dev/null path. See my post here for detailed instructions: http://forums.adobe.com/thread/1253800

  • ESYU: Autocreate issue를 위한 Debug file 생성 방법

    Purpose
    Oracle Purchasing - Version: 11.5.8 ~
    PO Autocreate issue 발생시 문제 해결을 위해 Debug file을 생성하는 방법에
    대한 설명을 목적으로 한다.
    Solution
    Autocreate debug utility는 11i_PRC_PF.H (patch 2320032) version 즉 11.5.8
    version 부터 가용하다.
    System Administrator로 log-in 후 specific user(autocreate 생성자) level로
    아래 profile options 값을 setting 한다.
    -. Set the FND Debug Log Enabled: Yes
    -. Set the FND Debug Log Level: Statement
    -. Set the FND Debug Log Module: PO
    Oracle Application을 log-out 후 위 profile option 값을 setting 한 user로 log-in을
    다시 한다.
    Autocreate를 통해 PO를 생성합니다. PO가 정상적으로 생성되거나 failed 될 것이다.
    Log file을 monitor 하는 방법:
    As System Administrator Go to Help-> Dignostics-> Logging -> View
    Search System Logs page가 pop up 될 것이다.
    특정 parameter나 아래 모든 parameters에 값을 입력 후 log를 view 할 수 있다.
    Level: Statement(optional)
    View : %PO_INTERFACE_S% ( For Autocreate)
    Posted After and Posted Before: Log를 보고자 원하는 date
    press GO
    다음 Module name을 가진 logs를 조회:
    %PO_INTERFACE_S%
    Download All을 이용하면 log file을 excel file로 export 할 수있다.
    Delete All을 이용하여 log statements는 remove 된다.
    Reference
    Note 220747.1

  • Prob. with doc registered under application other than SHIPPING EXECUTION

    Hi,
    We have a custom Pick Pack Slip report which we have registered under Custom Application.
    While Creating Document Set, if the document is registered under Custom Applicaiton, the document is not getting generated. (Concurrent program itself is not getting executed for this document) but if the document is registered under SHIPPING EXECUTION applicaiton, its getting executed.
    I have created one Document Set and while doing PICK RELEASE, I am using this document set. Initially I have attached only one document which belongs to custom application and ran pick release but it didnt submit any document. Then I added one more document which belogns to Shipping execution and submitted pick release one more time. This time it has executed program for the one belongs to shipping execution but not the custom one.
    If I register the same custom report to Shipping Execution, then its working fine !!! But I dont think this is the right approach to register all custom reprots to Oracle Shipping application.
    Please suggest !!!

    Yes..It won't work..I too tried it..
    Please open a TAR and work with oracle..
    Let's see what they are upto..

  • Debug mode configuration debug-file

    Hello,
    we have doployed a j2ee-application on was 7.0, netweaver2004s, SP11.
    Oon Tomcat and resin there are nor problems, but running uon was .7.0 there appear exceptions.
    How can we configure the debug-mode on was 7.0 and the debug-File?
    Best regards
    Oliver Prodinger

    Hi Oliver,
    Here is the link to the documentation:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
    HTH!
    -Vladimir

  • Custom Workflow for Shipping Execution

    Hi All,
    We have a requirement to cater approval on issuance i.e. at the time of shipping execution. For this purpose we have used Oracle Workflow Builder to cater the requirement. The workflow is working fine for approval but not for rejection. If we approve the shipping execution, the transaction is working fine but if we rejects it, the shipping transaction got stuck with exception and if we resolve the exception manually, we are unable to re send it for approval or even shipping.
    I will be grateful if anyone can help me out and advise me on how to setup of workflow for rejection.
    Thanks in advance.
    Regards,
    Zulfiqar Ali Mughal

    It is possible that the workflow has already been registered in db before you modified workflowActivities.xml.Did you try cleaning up workflow tables and restart the server??
    epub_workflow_info, epub_coll_workflow, epub_ind_wf,epub_wf_server_id tables
    Make sure there is only one entry for each workflow in epub_workflow_info. If there are multiple entries, then it may be coming from 2 different places and you need to disable one of them. Whenever you create custom work flow, copy the existing workflow and modify it and give it a different name. If you are importing programmatically, you really dont need to configure it in taskConfiguraiton.xml ( as it corresponds to settings related to which item-descriptors, tabs, security in BCC gui).
    -karthik

  • [SOLVED]Couldn't open file for 'Log debug file /var/log/tor/debug.log'

    Hello,
    I'm trying to run a tor relay on my arch linux box. Trying to launch the tor daemon, here's the log via
    $ systemctl status tor.service
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor v0.2.4.21 (git-505962724c05445f) running on Linux with Libevent 2.0.21-stable and OpenSSL 1.0.1g.
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.877 [notice] Read configuration file "/etc/tor/torrc".
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening Socks listener on 127.0.0.1:9050
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.909 [notice] Opening OR listener on 0.0.0.0:9798
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Couldn't open file for 'Log debug file /var/log/tor/debug.log': Permission denied
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [notice] Closing partially-constructed OR listener on 0.0.0.0:9798
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
    May 20 11:53:10 arch tor[21726]: May 20 11:53:10.000 [err] Reading config failed--see warnings above.
    May 20 11:53:10 arch systemd[1]: tor.service: main process exited, code=exited, status=255/n/a
    May 20 11:53:10 arch systemd[1]: Unit tor.service entered failed state.
    Why the tor daemon cannot write into /var/log/tor/debug.log ?
    Here's my /etc/group
    root:x:0:root
    bin:x:1:root,bin,daemon
    daemon:x:2:root,bin,daemon
    sys:x:3:root,bin
    adm:x:4:root,daemon,nue
    tty:x:5:
    disk:x:6:root
    lp:x:7:daemon
    mem:x:8:
    kmem:x:9:
    wheel:x:10:root,nue
    ftp:x:11:
    mail:x:12:
    uucp:x:14:
    log:x:19:root
    utmp:x:20:
    locate:x:21:
    rfkill:x:24:
    smmsp:x:25:
    http:x:33:
    games:x:50:
    lock:x:54:
    uuidd:x:68:
    dbus:x:81:
    network:x:90:
    video:x:91:
    audio:x:92:
    optical:x:93:
    floppy:x:94:
    storage:x:95:
    scanner:x:96:
    power:x:98:
    nobody:x:99:
    users:x:100:
    systemd-journal:x:190:
    nue:x:1000:
    avahi:x:84:
    lxdm:x:121:
    polkitd:x:102:
    git:x:999:
    transmission:x:169:
    vboxusers:x:108:
    tor:x:43:
    mysql:x:89:
    Last edited by giuscri (2014-05-20 12:18:56)

    SidK wrote:You must have modified your torrc to print to that log file. systemd starts the service as the tor user (see /usr/lib/systemd/system/tor.service). So if if you want to log to a file the tor user must have write access to it. By default however tor it set to log to the journal, which doesn't require any special permissions.
    Yes. I did edit the torrc file since I wanted the log to be store in that file. Indeed
    ## Logs go to stdout at level "notice" unless redirected by something
    ## else, like one of the below lines. You can have as many Log lines as
    ## you want.
    ## We advise using "notice" in most cases, since anything more verbose
    ## may provide sensitive information to an attacker who obtains the logs.
    ## Send all messages of level 'notice' or higher to /var/log/tor/notices.log
    #Log notice file /var/log/tor/notices.log
    ## Send every possible message to /var/log/tor/debug.log
    Log debug file /var/log/tor/debug.log
    ## Use the system log instead of Tor's logfiles
    Log notice syslog
    ## To send all messages to stderr:
    #Log debug stderr
    I missed the file systemd uses to choose who's the process owner.
    Course, I could edit /usr/lib/systemd/system/tor.service such that root will become the process owner; or, I could add the user I use everyday in the root group, then change the permission of /var/log/tor/debug.log such that it will be writable also for the folks in the root group.
    Yet they both seems to be a bit unsafe ...
    What is the best choice, to you guys?
    Thanks,

  • ORARRP with Win 2000 Terminal Services debug file

    Hi,
    I got no replies to my post of Dec 1 about ORARRP (1.3.4) directing output to a file instead of the virtual printer on Windows 2000 terminal services.
    Here is the debug file(orarrp.dbg) when a file named TS007 is written.
    Any help would be appreciated.
    Thanks,
    Dave Ball
    ORARRP: Full Command Line: "C:\Program Files\orarrp\orarrp.exe" "U:\orarrp_stuff\orarrp_tst.rrpt"
    ORARRP: Home Directory: C:\Program Files\orarrp
    ORARRP: INI File: C:\Program Files\orarrp\orarrp.ini
    ORARRP: Printing...
    ORARRP: Type=Text
    ORARRP: Direct Print to Printer
    ORARRP: Printer DeviceName = HP LaserJet 4L/NEO-630532/Session 12
    ORARRP: Printer Port = TS007
    ORARRP: Printer Target = HP LaserJet 4L/NEO-630532/Session 12, Printer Count = 1
    ORARRP: Enumerating printers:Printer = HP LaserJet 4L/NEO-630532/Session 12 Server = (null)
    ORARRP: Enumerating printers: Match = HP LaserJet 4L/NEO-630532/Session 12, Sharename =
    ORARRP: Local Printer attached to TS007
    ORARRP: Selected Printer = TS007 (HP LaserJet 4L/NEO-630532/Session 12)
    ORARRP: Selected Printer Port = TS007, Driver = HP LaserJet 4L
    ORARRP: PrintDlg Returned TS007
    ORARRP: Printing Direct
    ORARRP: Printer Opened
    ORARRP: Doc Opened
    ORARRP: Printed 486 Bytes
    ORARRP: Doc Closed
    ORARRP: Sending Extra FormFeed
    ORARRP: Printer Closed
    ORARRP: ** Debug Finished **

    I am using Tomcat 5.0.27 and it is working perfectly. perhaps check the stdout.log to see what errors are thrown while starting the tomcat. Check the port also

  • Shipping Execution vs WMS at upgrade time

    Hi,
    We are in process of upgrading from version 10.7 to 11.5.10. One big issue is whether we should tackle WMS implementation at our warehouse as part of the upgrade or stick with Shipping Execution and follow on with WMS as a separate project if appropriate. We had created our own "Distribution Module" in 10.7 that basically is a similar concept to Shipping Execution (with probably a little WMS). Anyway is there a white paper or any other information that anyone could provide to help make this decision?

    Hi, Carl,
    plhtyuk wrote:
    Hi everyone,
    is there a way to configure sqlplus such that when a statement (e.g. an INSERT) do not have a semi-colon at the end (or et / on the beginning of the next line) an error is returned?
    SET   SQLBLANKLINES  ONtells SQL*Plus that a single SQL statement can include lines that contain nothing but whitespace, or are completely empty.
    Here is an example:
    INSERT INTO emp (emp_no, emp_name) values (5, 'john')
    INSERT INTO emp_status (emp_no, status) values (5, 'full time');
    Running a script containing these two lines with sqlplus won't do the first insert and won't give an error.If SQLBLANKLINES is ON, then SQL*Plus will think all 3 lines above are part of the same SQL statement, and you'll get a syntax error. Neither INSERT will be done.
    By default these human errors are treated silently by sqlplus.
    I am almost sure there is no mean to detect that but in case I am wrong, I ask the question.There ought to be a more straightforward way to request warnings when you forget a ;. If it was up to me, I would have made that the default behavior.

  • Shipping Execution API

    dear all
    any one have shipping execution API documentation like wsh_trips_pub and othere
    Please provide
    Aamir

    Hi amir;
    Please check below which could be helpful for your issue:
    SHIP CONFIRM THROUGH THE SHIPPING PUBLIC APIs [ID 200396.1]
    backorder the delivery using shipping API [ID 807529.1]
    Unable To Update Mode Of Transport Through Standard Api [ID 295650.1]
    Getting Error While Calling Api Wsh_Trips_Pub.Create_Update_Trip [ID 738418.1]
    Also check below:
    Api's in EBS
    Re: Api's in EBS
    http://sairamgoudmalla.blogspot.com/2009/05/script-to-find-oracle-apis-for-any.html
    API
    Fixed Asset API
    List of API
    Re: List of APIs
    Regard
    Helios

  • Shipping Execution

    has anyone worked on shipping execution? is yes can someone share the setup document?

    Hi,
    Basically you have few setups that can be done in shipping execution or in Order management module.
    1. Shipping Parameters (Defined for Each Org) (Shipping --> Setup --> Shipping Parameters) or this can be defined in Inventory module as well.
    2. Picking --> PickSlip Grouping Rules ( Shipping --> Setup --> Picking --> PickSlip Grouping Rules )
    3. Define Release Sqeuence Rules ( Shipping --> Setup --> Picking --> Release Sqeuence Rules )
    4. Define Release Rules form ( Shipping --> Setup --> Picking --> Release Rules form )
    5.Document Categories (Shipping --> Setup --> Documents--> Document Categories (Define Bill of Lading, Packing Slip report)
    6. Document Sets (Shipping --> Setup --> Documents--> Document Sets )
    where reports are generated at Ship Confirm & Releasing Orders.
    Reports such as
    1. Commercial Invoice
    2. Bill of lading
    3. Packing slip Report
    4. Vechile Load
    5.Mailing label
    The above mentioned are reports for Ship Confirm. maynot be every Org might not be using all five.
    6. Grants and Role Definitions (Shipping --> Setup --> Grants and Role Definitions --> Grants)
    This is very important for shipping grants. if the user is not assigned. In shipping transaction form the buttons willl be greyed out.
    please let me know if you need more information.
    Kalyan.

  • I cannot print a shipping label pdf file - there is no print button, and when I choose print preview, the page is blank

    I used to be able to print shipping labels from Amazon.com. The label image is a pdf, but on the pdf page there is no print button. When I go to file print preview in the main tool bar, the image shows the file name, but no shipping label.

    You can't delete pages with Reader, only with Acrobat.

  • How to debug file content conversion problems?

    Hi,
    I'm trying to debug a file content conversion problem.  I'm mapping a few nodes in an IDOC to a file of fixed length fields.  I'm using the "<Node A>.fieldFixedLengths", "<Node B>.fieldFixedLengths", "<Node C>.fieldFixedLengths", etc. parameters to specify the fixed length records.
    However, a certain node (for e.g. Node B) is causing a problem and if it is present in the IDOC, the output file does not get created.  Upon checking the XI monitor, I notice that the file gets mapped correctly and thus the problem lies when the file adapter does the file content conversion.  How do I debug this because there is no descriptive error in the XI log?  If this node is not present, the file gets generated fine.
    Thanks,
    Basant Gupta

    Hi,
    If your SXMB_MONI shows, success status, then go to RWB->Message Monitoring->Message display tool and then check Audit log for the analysis,
    So it wil help you debug the situation.
    If there is no error, then check RWB->Component Monitoring->Adapter Monitoring for you file communciation channel..
    /people/michal.krawczyk2/blog/2005/01/02/simple-adapter-and-message-monitoring
    Regards,
    Moorthy

Maybe you are looking for