Business Partner Contact Numbers

 

 

Debug Mass Activity Transactions (DBUG)

SAP has a reserve command DBUG for you to debug mass activity transactions such as FPVA (Dunning Proposal).

Once you enter DBUG at command field and hit return key.


You will see this Pop Up Message.


When you start running the program, the debugger will be launched.

Tips on ISU_FINDER - Part 2

ISU_FINDER's EFINDPAR structure contains a lot of date field, so what do they mean? Basically, ISU_FINDER use these date field to search for object in their respective areas, some important date field as per below:

• EVER-EINZDAT             <= V_DATE_TO  
• EVER-AUSZDAT             >= V_DATE  
• V_EANL-AB                <= I_DATE
• V_EANL-BIS               >= I_DATE 
• EASTL-AB                 <= D_DATE 
• EASTL-BIS                >= D_DATE 
• V_EGER_H-AB              <= D_DATE 
• V_EGER_H-BIS             >= D_DATE 
• EGERR-AB                 <= D_DATE 
• EGERR-BIS                >= D_DATE 
• EABP-BEGPERIODE          <= U_DATE 
• EABP-ENDPERIODE          >= U_DATE

Debugger Variant

Debugger Variant allow you to save your current debugger layout, breakpoints, settings, and options into database or file. These components can be loaded again at later days. This comes very handy especially when your project team involves offshore support, or you need to pass the problem that you were working on to your co-workers. By default, there is a debugger variant named START_UP which is always loaded when you start the New ABAP Debugger. You can overwrite this debugger variant if you want to load the current setting every time you launch the debugger. Otherwise, you can save it with other name and then load it via Debugger -> Debugger Session -> Load when you need it.

For Example, I want to find out why and when SAP that flag EABLG-UNTERDR to 'X'. Thus, I use where-used list to find out all the program.

As you can see there is a lot of programs changing the value of this field. It would be troublesome if I want to debug same pieces of code again in the future. Thus, after setting the session breakpoint, I launch debugger.


And I go to save debugger variant.

Next time, when I launch debugger again. I will just need to go to Debugger Session and then load the debugger variant and all the break points are waiting for me now.

FREE_SELECTIONS_WHERE_2_EX

This FM works the other way round from FM 'FREE_SELECTIONS_EX_2_WHERE'. It converts select statement's where condition into expression that you can use in FREE_SELECTIONS_EX_2_WHERE. I re-use the example in my previous post here.
Conditions:
WHERE hvorg EQ '0600'
AND ( tvorg EQ '0010'
OR tvorg EQ '0011' )
AND augst EQ ''
AND augrd NE '05'. 
 
Input:

Result:

Request Protection Function in SE10

You can protect your request to avoid other people to add more users. You can go to Request/task -> Request -> Protect to do so, alternatively you can right click on your request and then choose protect or use function key Ctrl + F2

To remove the protection, choose Remove Protection.

How to assign Shop Paper?

1. Go to SPRO -> SAP Customizing Implementation Guide -> Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Basic Settings -> Print Control -> Define Shop Papers, Forms and Output Programs.

2. Choose Assign Permitted Shop Papers

3. Choose Work Area "N" (Notification (PM/QM..))

4. You will find the Document Type = Notification Type, Shop Paper Name, Selection Text for Shop Paper and Selected Indicator.

Maintenance View: V_T390_O [Shop Papers Allowed by Order Type or NotifType] Tables: T390_O [PM: Shop paper control by order type], T390 [PM: Shop papers for print control], T390_OT [Description of shop papers per document type selection],

Document Type

The document type classifies the accounting documents. It is stored in the document header.

Attributes that control the entry of the document, or which are they noted in the document, are defined for each document type. In particular, the number range assigned to the associated documents is defined on the basis of the document type.

Extraction from SAP.

Normally, field name for document type is BLART.

CRM Middleware Flow

From R/3 to CRM

1. At R/3, data stored in BAPI structure and written to an outbound queue
2. Inbound Queue in CRM has the same name as Outbound Queue in R/3, same queue is used for same objects
3. R/3 inbound Adapter convert data received by CRM to a uniform internal format, by using mapping function module to read data from BAPI structure and converts it to an mBDOC (messaging BDoc) 
4. mBDoc is saved in BDoc store in CRM
5. Validation performs checking using validation service, it calls up the check of CRM application which is used for dialog users too
6. Data is saved to Online Database if no errors. Somebody needs to check several times a day to make sure all errors (BDoc validation error) are solved.

 From CRM to R/3

1. Data Validation by CRM application
2. A mBDoc includes the change is created and saved in CRM
3. The change made is written to a CSA queue. CSA queue provides data in CRM system to other systems.
4. Replication Service is called that determines systems to which the changed data is to be sent
5. R/3 outbound adapter converts mBDoc data to a BAPI structure
6. Outbound queue in CRM collect data and keep the processing in CRM separate from further processing in R/3
7. The data is transferred sequentially to R/3.

EFCS - Form Class Maintenance (Part 2)

Example of Form Class:

• IS_U_CA_DUNNING

• Dunning Notice

• IS_U_CA_INSTPLAN 

• Installment Plan Notification

• IS_U_BI_BILL

• IS-U Bill

• IS_U_DM_MR_ORDER

• Print Meter Reading Order

How to configure Shop Paper (Print Program & Forms)?

1. Go to SPRO -> SAP Customizing Implementation Guide -> Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Basic Settings -> Print Control -> Define Shop Papers, Forms and Output Programs.

2. Choose Define Shop Papers

3. Choose Work Area "N" (Notification (PM/QM..))

4. You will find the Output Program (for e.g. "RIPRAT00") and the Form name ("PM_COMMON")

Maintenance View: V_T390 [Shop Papers] Tables: T390 [PM: Shop papers for print control] T390_T [PM: Shop paper description]

SREL_GET_NEXT_NEIGHBORS (Part 1)

CALL FUNCTION 'SREL_GET_NEXT_NEIGHBORS'
*"  IMPORTING
*"     VALUE(OBJECT) LIKE  BORIDENT STRUCTURE  BORIDENT
*"     VALUE(ROLETYPE) LIKE  RELROLES-ROLETYPE OPTIONAL
*"     VALUE(RELATIONTYPE) LIKE  BRELTYP-RELTYPE OPTIONAL
*"     VALUE(MAX_HOPS) TYPE  RELHOPS DEFAULT 1
*"     VALUE(BYPASS_BUFFER) TYPE  FLAG DEFAULT SPACE
*"  TABLES
*"      NEIGHBORS STRUCTURE  NEIGHBOR OPTIONAL
*"  EXCEPTIONS
*"      INTERNAL_ERROR
*"      NO_LOGSYS

This FM returns 2 objects that have binary relationhips. 1 of the example we have in SAP IS-U is Disconnect Document and the Service Notification.

1. Enter Object Key and Object Type of a Service Notification

2. Enter Role Type and Relationship Type of the object. Please take note that this is optional.

3. It returns Disconnection Document Number + Disconnection Activity Number 

Tables involved:

• SRRELROLES
• ORBRELTYP
• SMZB_BINREL 

Correspondence history - CORRHIST

Editor Lock

Editor Lock prevents other people to modify your program. Somehow, there are cases where you forget to remove it. What happened if other people want to modify your program in the future, but you are no longer involved in that system?

I found 2 blogs provide solution that is quite useful:

1. ABAP Program to Lock/Unlock the ABAP Editor Lock Field 
2. SAP ABAP Program EDITOR LOCK/UNLOCK 

Both of them are doing the same thing. Ultimately, you just have to update the record in table TRDIR, set the field EDTX = 'X' if you want to lock it, and set it SPACE if you want to unlock it. 

Print Immediately is Blank?

Most of the time we rely on print parameter to make some decisions in form printing, one of the odd scenario that you have to be careful when you are developing application form is when you have a choose print parameter dialog screen as per following (EA60):

If you set "Output After Last Document" (LAST_DOC_ACT), FM 'EFG_PRINT' will clear the value of field TDIMMED and TDFINAL. (source code: line 516 to line 519). Thus, no matter how hard you set "Print Immediately" in the following screen:

C-ITCPO-TDIMMED and C-ITCPO-TDFINAL will always be blank in application form.