T.C : SE38 --WHAT IS ITS RELEVANCE IN SD

[Former Member]

hi sapgurus

what is the relevance of tc se38. what kind of reports we can generate and how to use it more effeciently. if anybody has a listing of reports which can be run on se38.

my mail id usekhar_win@yahoo.co.in

also, what is a condition record? and related material

pls mail me on these subject asap.

thanks in advance.

[Former Member · Accepted solution]

for cond records refer the link

http://help.sap.com/saphelp_470/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm

[Former Member]

Dear Sekhar,

SE38 is ABAP Editor.

ABAP Editor is a source-code editing tool designed to handle the specifics of ABAP coding. It is one of the main components of the ABAP Workbench.

You use the ABAP Editor to create and edit your programs and their components (Programs related to SD in your case).

Visit the following link for more information regarding ABAP Editor:

http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abap+development

Reward points if this helpful.

Regards,

Naveen.

[madhan_narlapuram]

SE38 is for writing abap programs

SE37 for function modules ...

thanks

madhan

[Former Member]

Hi Sekhar

used to create userexits like VOFM: Requirement and Formulas for SAP-SD Pricing

For complex reports specifications, SAP allows you to write customize ABAP/4 programs.

ABAP/4 allows SAP programmer more freedom in how they want to code the programs.

There are no one size fixed all software, with this in mind, SAP allows its users to create their own dialog or reports programs using the language ABAP/4.

Some Development transaction code are :-

SE38 - ABAP Editor

SE37 - Function Builder

<b>

e.g.</b>

Steps to Create Commission for Agent

For creating commission agent, you have to follow below steps.

1) Establish Partner Functions for the Commissionee(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

2) Assign the Partner Functions to Partner Procedures

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

3) Create a Partner Procedure for the Commissionees

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

4) Create New Customer Account Group(s) for Commission Agents

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; LOGISTICS GENERAL ->; LOGISTICS BASIC DATA: BUSINESS PARTNERS ->; CUSTOMERS ->; CONTROL ->; DEFINE ACCOUNT GROUPS AND FIELD SELECTION FOR CUSTOMER

Transaction Code: OVT0

5) Assign the Partner Functions to the Customer Account Group(s)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS ->; GOTO ->; PARTNER FUNCTIONS ->; ENVIRONMENT ->; ACCOUNT GROUP ASSIGNMENT

Transaction Code: VOPA

6) Assign the Partner Functions to the Partner Procedure for the Sales Document Header

Menu Path: Tools ->; Business Engineer ->; Customizing ->; Sales and Distribution ->; Basic Functions ->; Partner Determination ->; Define Partner Functions

Transaction Code: VOPA

7) Assign the Partner Functions to the Partner Procedure for the Sales Document Item (OPTIONAL)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PARTNER DETERMINATION ->; DEFINE PARTNER FUNCTIONS

Transaction Code: VOPA

😎 Edit the Pricing Communication Structure (KOMKAZ) to Hold the New Functions (Client Independent)

Menu Path: Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; DICTIONARY

Transaction Code: SE11

9) Edit MV45AFZZ – userexit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

10) Edit RV60AFZZ - userexit_pricing_prepare_tkomk (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

11) Edit MV45AFZB - userexit_new_pricing_vbkd changing new_pricing (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

The following code should be inserted into program MV45AFZZ to allow the system to re-execute pricing if the user makes a change to the relevant partner function (alteration, addition, deletion).

13) Add the KOMKAZ Fields to the Pricing Field Catalog (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES

Transaction Code: OV24

14) Create Condition Tables (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES

Transaction Code: V/03

15) Create an access sequence containing the new tables (Client Independent)

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE ACCESS SEQUENCES ->; MAINTAIN ACCESS SEQUENCES

Transaction Code: V/07

16) Create a new condition type

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE CONDITION TYPES ->; MAINTAIN CONDITION TYPES

Transaction Code: V/06

17) Add the Condition Type to the Pricing Procedure

Menu Path: TOOLS ->; BUSINESS ENGINEER ->; CUSTOMIZING ->; SALES AND DISTRIBUTION ->; BASIC FUNCTIONS ->; PRICING ->; PRICING CONTROL ->; DEFINE AND ASSIGN PRICING PROCEDURES ->; MAINTAIN PRICING PROCEDURES

Transaction Code: V/08

11) Create Commsission Report ZZCOMMISSION (Client Independent)

Menu Path: TOOLS ->; ABAP WORKBENCH ->; DEVELOPMENT ->; ABAP EDITOR

Transaction Code: SE38

[Former Member]

Hi Shekhar,

In connection to my above mail..

Condition Record is the Value Records which we maintaine using T.code VK11. All the Condition types which we use need to have some value to be maintained sothat it will show the value in the Sales Documents. Like Price, Discounts, Frieghts, Taxes etc. All these values are need to be maintained in VK11. So those records are calles as Condition records.

These Condition records are maintanied using different combinations like customer wise, material wise, sales org wise, dist channel, customer group, material group etc

REWARD IF HELPFUL.

Regards,

Praveen

[Former Member]

Hi Shekhar,

SE38 is the T. Code used to Create / Change /Display any programme.

This is used irrespective of any module. For Technical Consultants its very much useful T.code to create Programmes.

If we want to run any Transaction in SAP, it requires a Programme to run in back ground. That Programme is created in SE38. And using the T.code SE93 we can create Transaction code for that Programme.

For example to create Sales Documents we use T.code as VA01. Here also once after using VA01, it will run a standard programme SAPMV45A. This programme is created in SE38 only.

Even if the System is going into dump while running any Transaction / Programme etc, then we can check the error using SE38.

And this is also useful to create Reports such as

SD correction reports like

SDRQCR21

SDVBUK00

Reports used in Scheduling Agreements and Thirtd-party orders like

SDLIPL01

SDBANF02

Hope this will give some idea.

REWARD IF HELPFUL.

Regards,

Praveen

[Former Member]

Dear Sekhar,

in the transaction SE38 you can create, change or display the ABAP programs (subroutines, reports, main programs), but not the function modules for which the transaction SE37 is intended.

Directly from the transaction SE38 you can start also reports; for example, SD correction reports or SD analyting reports (as example, SDRQCR21 for correcting requirements, SDVBUK00 for correcting the status entries, SDLIPL01 for reconstructing cumulative quantities in scheduling agreements, SDBANF02 for analyzing inconsistencies in third-party orders etc. etc.). Here you can start also your own reports.

Also from transaction SE38 you can see the main SD programs like SAPMV45A and their subroutines.

There is no special relevancy of this transaction to SD. It is a general ABAP transaction.

I hope, this info helps.

Kind regards,

Akmal Vakhidov

Development Support SD ERP, SAP, Walldorf/Germany

[Former Member]

Hi Sekhar.,

T.code SE38 regenerated a programme,In a programme we have tables & Fields ,So when we executes the programme,It willregenerates,Condition record is that we maintain some conditions for example in VK11,that a particular customer we need to charge particular price that is a condition record

REWARD if helpfull

Thanks & Regards

Narayana