Watch point on a special field

Hi All,
I have got an exited idea, but when I try to do it, I have problem. The idea is to set watch point on special field SY-REPID. And the watch point condition is SY-REPID = <Program_Name_I_Want_to_step_In>. But I fail to set watch point to the field sy-repid. Othewise we can step into whatever program we want to step in so that we can set watch point to any variable of that program.

You can set a watch point on something like sy-subrc and it will stop whenever the value changes in any program that is called.
(But this won't work with sy-repid, because you cannot set a watchpoint on it. Try setting a watchpoint on SY-XPROG instead.)
Rob
Edited by: Rob Burbank on Oct 26, 2009 10:53 AM

Similar Messages

What is watch point and break points?what are there types?

what is watch point and break points?what are there types?

Static Breakpoints
Static breakpoints are always user-independent if there is no specification of a user name. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application when program execution is always to be interrupted at the same place. For more information, refer to the chapter Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints because you can deactivate or delete them at runtime. They have the following advantages:
· You do not have to change the program code.
· You can set them even when the program is locked by another programmer.
· You can define a counter that only activates the breakpoint after it has been reached.
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For more information, refer to the chapter Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Watch point are used to put logical break point for a certain condition..Example..If you want to know when the internal table is getting append..Then you have to give the program name and the internal table in the watch point..
Steps to create a watch point.
Start debugging '/H'.
In the debugging screen press the create watch point button in the application tool bar..
In the program give the program name..
in the field give the field name.
In the relational operator given '='
In the comp. field/value give the value ..
Hope this helps..
Regards,
Parvez.

Break points and watch points

Hi all
 Can anybody help me using break points and watch points.what do they exactly do as well..
Thanks
abap user

Hi
Breakpoints
Instead of starting an ABAP program directly in the Debugger, you can also debug a program by creating one or more breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoint
at statement The Debugger stops the program directly before the specified statement is executed.
Breakpoint at subroutine The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module The Debugger stops the program directly before the specified function module is called.
Breakpoint at method The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Use
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted a BREAK-POINT statement in an ABAP program, the system always interrupts the program at that point. You should only use static breakpoints during the development phase of an application. You should set static breakpoints whenever more than one programmer is working on the same program and you always want to stop the program in the same place.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. You should, therefore, use them when you only want the program to be interrupted when you run it yourself. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
 You do not have to change the program code
 You can set them even when the program is locked by another programmer
 You can define a counter (for example, only activate the breakpoint after it has been reached five times).
Special Dynamic Breakpoints
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the program code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger.
Transferring Breakpoints to HTTP and Update Sessions
If an HTTP or update session is called from a Logical Unit of Work (LUW), new work processes are started for these new sessions. Breakpoints that were defined beforehand in the calling LUW are copied to these sessions where they can be displayed under breakpoints.
If, for example, the update module func is called via CALL FUNCTION func IN UPDATE TASK, the new work process is displayed in a second window if Update debugging was selected under Settings in the debugging mode. All the breakpoints that were set in the calling LUW can then be processed here.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC <> 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities  Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
1. Position the cursor on the line of the source code at which you want to set the breakpoint.
2. Choose Utilities  Breakpoints  Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities  Breakpoints  Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
1. Position the cursor on the line in which you want to set the breakpoint.
2. Select the line by double-clicking it or choosing Breakpoint  Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.

Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1. Choose Breakpoint  Breakpoint at  Statement...
2. Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3. Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
1. Choose Breakpoint  Breakpoint at  Event/Subroutine.
2. Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
1. Choose Breakpoint  Breakpoint at  Function module...
2. Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
3. Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint  Breakpoint at  System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint  Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
 By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
 By choosing Breakpoint  Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto  Control debugging  Breakpoints.
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint  Set/delete. To delete all breakpoints, choose Breakpoint  Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint  Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
 You can set up to five watchpoints in a program.
 You can also specify the conditions on which a watchpoint is to become active.
 You can specify logical conditions between up to five conditional watchpoints.
 You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
 You can change and delete watchpoints.
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
1. Choose Breakpoint  Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears.
2. Decide whether you want to set a local or global watchpoint.
3. Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
4. If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
5. To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator Meaning
< Less than
<= Less than or equal
= Equal
<> Not equal
>= Greater than or equal
> Greater than
6.
7. You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR Only one of the specified conditions must be met
AND All of the conditions must be met.
To create a logical link between watchpoints:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to open the watchpoint display.
2. Set the Logical operator between watchpoints option.
The default value is always OR .
Changing Watchpoints
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the pencil icon in the line containing the watchpoint you want to change.
3. Change the watchpoint attributes in the Create/Change Watchpoint.
3. Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint  Delete or Breakpoint  Deactivate/activate. Instead, proceed as follows:
1. Choose Goto  Control debugging  Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
2. Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
Reward ifusefull

FAGLL03 Special Field Values Do Not Display in Production

We are using the new GL in ECC 6. I have a strange problem where special fields that were added to the line item transactions display in dev and quality but not in production. Please read the steps that I have taken.
1. Using note 984305 we defined special field BSEG-MATNR using this path:
Financial Accounting (New)
General Ledger Accounting (New)
    Master Data
      G/L Accounts
        Line Items
          Define Special Fields for Line Item Display
This field (U_MATNR) displays correctly in FAGLL03.
2. I used note 1034354 to create an implementation of BAdI 'FAGL_ITEMS_CH_DATA. Then I
followed the documentation of the BAdI to create structure CI_FAGLPOSX within FAGLPOSX and added these fields:
Material Type: field MARA-MTART
Material Group: MARA-MATKL
I added code to method CHANGE_ITEMS to read for those fields. Here's part of the code:
* MARA - Get Material Type and Material Group
    SELECT SINGLE mtart matkl
      FROM mara
      INTO (wa_items-zzmtart, wa_items-zzmatkl)
      WHERE matnr = wa_items-u_matnr.
The values of these fields display correctly in development and quality, but they do not display in production.
3. When I debugged FAGLL03 in development I found that the value of U_MATNR was filled when I stopped at method CHANGE_ITEMS. However, when I debugged in production, U_MATNR was not filled. It had to be filled at a later time because the value appears on the report. In my code, I am using U_MATNR to find the values of material type and material group. Because U_MATNR doesn't have a value at that point in time in production, my code doesn't find material type or material group.
4. I contacted SAP and was instructed to use note 984305. I executed the function module
ITEM_STRUC_EXTENSION which did not help.
5 I also used note 205096 to execute report BALVBUFDEL, but this did not help either.
6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
7. I tried to compare configuration between development and production, but everything looked OK to me.
Has anyone had this problem? Any tips?
Brenda

Hi Brenda,
>
Brenda Bankert wrote:
> 6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
I have no idea except that you can make sure Include CI_FAGLPOSX is active as well as the including FAGLPOSX. And please check the transport protocol(s) if CI_FAGLPOSX is included. If you have any kind of error/warning in the import protocol, that may give you a hint.
If nothing helps, create a new sap support case and tell them you are using SAP solutions without modifying anything.
Regards,
Clemens

How to create watch points in ECC 6.0

Hi Experts,
How to create watch points in ECC 6.0
Thanks.

Dear Kalyan,
The moment the debugger starts, there will be an icon for "Watchpoint" exactly after F5, F6, F7, F8 and a big STOP red button on the application tool bar. Once you click on that Watchpoint button, it will take you to the screen where you need to define the exact field and its relative operator along with the condition to be checked.
Hope this is clear. No navigation needed for this.
-Syed.

Regarding watch points in ABAP debugger

Hi,
Could u explain , why we use watch points, what is the use of it
and how to use it.
Thanks & regards,
[email protected]

Watch points
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/14/6d1c370c468b7be10000009b38f936/frameset.htm
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
You can set up to five watchpoints in a program.
See also Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
You can change and delete watchpoints.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
ashish
Message was edited by:
Ashish Gundawar

Watch points

Hi all,
I know that there are two ways of debugging in ABAP. One is setting the breakpoints and the other is watchpoint.Can anyone please explain me what is watch point, what is the need of going for that when we have debugging option, And how to work with watch point ? what is the difference between local and global watch point.
Regards,
Varun.

Hi Varun,
watch points are used explicitly to stop for a particular record with some value.
say i have 10000 records , i am looping that itab, i cannot say F5 , to see for a particular record, in that case we will create watch point on itab-field which is equal to some value , when you say F8, then it will stay exactly that particular record.
it will save the debugging time.
for more info read this SAP help ..
http://help.sap.com/saphelp_webas610/helpdata/en/c6/617ce2e68c11d2b2ab080009b43351/content.htm
regards
vijay

To show a special field on the ME2K report

Hi everyone,
The question is about adding a field in the ME2K report. In the layout is needed the PO status, that is wether the PO is still open/completed or not. I was taught dynamic selection can be used to filter by the 'Delivery Completed' criteria, however the info does not appear on the report when doing this way. Is there a way, excl. programming a new transaction, to have the 'Delivery Completed' field appearing on the report? Are special fields available for ME2K?
Many thanks and regards,
SB

to close

File Name and Path special field

Post Author: puser01
CA Forum: .NET
I have a report created in CR 9 with the File Name and Path special field on the report displayed correctly. when i try to run it on CR XI environment i get this:
C:\WINDOWS\TEMP\{4D86438D-54F5-4EEF-A0AB-05D5EB2BFF35}.rpt
How can i correct this?

Our installer names don't make it easy for the new user, or the seasoned veteran for that matter. Although both those installers have 2008 in the name, they are for entirely different products.
CRRedist2008_x86.msi
This MSI installer is used to install the runtime for Crystal Reports Basic for Visual Studio 2008 - version 10.5.
cr2008fp35.exe
This installer package is used to install the CR .NET runtime for Crystal Reports 2008 - version 12.3.
Since you've updated your development system to Crystal Reports 2008 you'll only want to use the runtimes listed on this reference page - http://www.sdn.sap.com/irj/sdn/crystal-xcelsius-support?rid=/webcontent/uuid/10e38d93-7f07-2d10-beae-e739182f8ada. [original link is broken]
I suggest either of these
SP 3
https://smpdl.sap-ag.de/~sapidp/012002523100007123592010E/cr2008sp3_redist.zip
FixPack 3.5
https://smpdl.sap-ag.de/~sapidp/012002523100006341772011E/cr2008fp35_redist.zip

Line item display-special fields

Hi,
i selected a special field for fbl5n and saved in a new lay-out.When i select the particular lay-out special field values are displayed .
But when i default the layout , system not displaying the values though the field is avilable.
regards
Guru

Hi meena,
search below link useful yours.
scn.sap.com/docs/DOC-45019
scn.sap.com/docs/DOC-49772#comment-439481
https://scn.sap.com/thread/1636245
Thanks,
G Rajendhar.

Adding Special Field in the line item display

Dears Through SPRO settings, I added the field 'Group Account Number' (ALTKT) for the GL line item display.
It is now transported to Quality.
When I try to see that field in the change line item layout, I could not find that field for inclusion.
However, in the SPRO of Quality, I find that field already appearing.
Why it is not appearing in the FBL3N special field screen ?

Hi Niki,
I am not sure how you have added this filed but if you follow these steps you will have it.
1- Run FBL3N and make your settings and execute it (F8).
2- Go menu Settings > Special fields (You can run it by t code OBVU out of FBL3n also)
3- Add a new entry, select your field (BSEG ALTKT Group account number) and save it
4- Back one step (F3) and select "Change layout..." icon.
Now you have the field in "Hideen fields" column. Just select it as "show selected fields"
Regards,
Omid

Using Special Fields in Formula's

Hello,
I'm trying to use a Crystal "Special Field" to filter data in my report. Specifically, I want to use the "Current CE User Name" field to achieve row-level security. Does anyone know how to use these fields in parameters or filters?
Regards,
Gilbert

You can use the special field CUrrentCEUserName like this
If (IsNumeric(Right(CUrrentCEUserName,3))) then
ToNumber(Right(CUrrentCEUserName,3)) = {dbvalue}
else
ToNumber(Right(CUrrentCEUserName,2)) = {dbvalue}

How to use RECNUM special field in a file bulk load interface (sqlldr)

Hi,
I'm trying to load an ordered set of full text lines from a flat file using Sql Loader 11.2 with ODI 11.1.1 bulk LKM (LKM File to Oracle - SQLLDR).
I have to keep track of each line number in a separate target table column NUM_SEQ and feed it with sqlldr RECNUM special field.
I haven't found any other way to do that but to tweak manually the generated sqlldr .ctl control file (bad but it works) :
NUM_SEQ RECNUM,
FULL_LINE CHAR(4000)
I've tried to map "RECNUM" as an expression in the map tab of the loading interface but the column itself gets discarded at .ctl generation.
I haven't found any mention of RECNUM in the whole ODI documentation, neither on this forum nor the Web.
Using an internal Oracle sequence in the subsequent steps of the ETL breaks the garantee of ordered lines.
Any hint ?

You will have to enhance the KM so that this clause gets added to the CTL file each time.
Add an Option to the KM in which you can specify name of the column that you want to act as line_number.
And then in the KM, change the "Generate CTL File" step and add
*<%=odiRef.getOption("RECNUM") %> RECNUM*
after the call to the <%=odiRef.getColList(" ") %> API
So, this will add the RECNUM column to the list of the columns generated.

Special fields for FAGLL03

Hi,
I need to add Purchase order, vendor, vendor name, customer, customer name and ar invoice field as a special field for FAGLL03.
I am able to add vendor, customer and purchasing number fields but I am not able to find name field for customer and vendor. Also I was not able to find ar invoice field.
Any help will be apprecaited.
Thanks,
Mark

Hello Mark,
Here at our side this has been implemented this way. You will need ABAP consultation:
1) Create an append structure in RFPOS structure with the new desired fields;
2) You will have to use a BTE to implement the exit. Ask the ABAPer to create a new Z function module based on existing SAMPLE_INTERFACE_00001650.
3) Through transaction FIBF, Menu Settings -> Products -> ...of a customer, you should create a code to identify the customization. Lets say FIN01. Don't forget to click on checkbox field to activate the business transaction event.
4) Through transaction FIBF, Menu Settings -> Modules P/S -> ...of a customer, you should create an entry to assign the Z function module with the product. Something like below:
Event Product Ctr. Appl. Function module
00001650 FIN01 FI-FI Z_INTERFACE_00001650
Hope it helps you.
Regards,
Daniel
Edited by: Daniel Carvalho on Oct 2, 2009 5:14 PM

Add a special field called gsber

Hello AL,
I want to add one special field called gsber in to vendor line item display report, i'm using standard report define additional fields for line item display(SPRO).
but its not allowing me to do so, pls let me knw what can be the reason
Thanks
Sunny

Hi,
Look at the BADI's
CUSTOMER_ADD_DATA ans CUSTOMER_ADD_DATA_CS
Regards
Sudheer

Watch point on a special field

Similar Messages

Maybe you are looking for