BADi used for creating customer own data in transaction me52n

Hi experts,
please any one tell me what is the procedure for creating or changing. How to get access for customer own data in transaction me52n. How to get authorization checks.
thank you,
regards
vijay krishna

Hi
check this link.
Name of Badi used with transaction ME52N
Thanks
Viquar Iqbal

Similar Messages

What are the methods used for creating customer

i have to upload a text file and create customer using idoc .can any one suggest the methods used to fullfil this requirement

Hi,
Upload the file using the function module GUI_UPLOAD into an internal table then try to pass the values from the file to the segments in the idoc DEBMAS03 using the function module MASTERIDOC_CREATE_DEBMAS to create the customer.
Any doubts regarding you can clarify.
Thanks&Regards
Sarves

User Exit OR Badi for MK01 transaction (used for saving vendor amster data)

Hi All,
I have a requirement where I have to call my workflow, when we create the Vendor using my custom transaction (ZMK01, which is a copy of standard transaction MK01).
For Workflow triggering I am using FM 'SAP_WAPI_CREATE_EVENT' in the user exit 'EXIT_SAPMF02K_001' but this is only for checking the data on saving Vendor Master.
So I want to use FM 'SAP_WAPI_CREATE_EVENT' at right place. For that , I need User-Exit or BADI which is used for saving vendor master data.
Could anyone please help me to find out the user exit or BADI for save event of vendor master data using transaction MK01.
Looking forward to your advise and thanks in advance.
Best Regards,
Mamta

Hi ,
I forgot to activiate the project linked with User exit 'EXIT_SAPMF02K_001' .
so problem is solved now
Thanks,
Mamta

How to create customer master data for walking customer in retail

hi experts !!!!!!
for retail industry e.g books trading industry
how to create customer master data for walking customer in retail
its dummy or one time customer
if i create one time customer then same customer number can i use for every new order and every new customer how ?????
thanks

Dear Hanumant,
As per my view,,
You can use one time customer functionality to full fill your requirement.
When you create sales order with one time customer system take you to the customer data maintanence screen through that you can maintain the one time customer data.
Same one time customer number you can use for every new order through maintaining different data.
I hope this will help you,
Regards,
Murali.
Edited by: Murali Mohan.Tallapaneni on Dec 19, 2008 6:08 AM

What Function Module can be used to create vendor master data in SAP R/3?

Hello -
I've been trying to find a standard SAP delivered BAPI that can be used to create vendor master records in ECC 6.0. Up to this point I have not been able to do so. With SAP MDM solutions and SRM solutions it seems logical that SAP would deliver a standard BAPI that can be used to create vendor master records in the ERP/R3 environment (similar to the BAPI_MATERIAL_SAVEREPLICA for creating material master data records).
I have been able to find BAPI_VENDOR_CREATE but this only calls the online transaction and does not offer much additional functionality beyond what transaction code XK02 already offers.
The next best alternative appears to be IDOC_INPUT_CREDITOR but our preference would be to not use IDOCs for the project we are working on.
Can anyone offer any insight or personal experience on how vendor master records have been successfully interfaced with SAP R/3? Did you have to use IDOCs or create a custom RFC call? Thanks for the help!
Rich Wortmann
<< Personal information removed >>
Edited by: Rob Burbank on May 14, 2009 10:43 AM

Quite a gap in the BAPI arsenal. I think the options are IDoc, which you don't want, good old program RFBIKR00 (requires flat file for input, can be used via LSMW) or DIY (very complex).
Thomas

Procedure for creating transparent table, data element and domain

Hi,
Can anybody let me know the procedure for creating transparent table, data element and domain.
Thanks,
Mahathi

Hi
Database table and its components
A database table is the central data structure of the ABAP/4 data dictionary.
The structure of the objects of application development are mapped in tables on the underlying relational database.
The attributes of these objects correspond to fields of the table.
A table consists of columns (fields) and rows (entries). It has a name and different attributes, such as delivery class and maintenance authorization.
A field has a unique name and attributes; for example it can be a key field.
A table has one or more key fields, called the primary key.
The values of these key fields uniquely identify a table entry.
You must specify a reference table for fields containing a currency (data type CURR) or quantity (data type QUAN). It must contain a field (reference field) with the format for currency keys (data type CUKY) or the format for units (data type UNIT). The field is only assigned to the reference field at program runtime.
The basic objects for defining data in the ABAP Dictionary are tables, data elements and domains. The domain is used for the technical definition of a table field (for example field type and length) and the data element is used for the semantic definition (for example short description).
A domain describes the value range of a field. It is defined by its data type and length. The value range can be limited by specifying fixed values.
A data element describes the meaning of a domain in a certain business context. It contains primarily the field help (F1 documentation) and the field labels in the screen.
A field is not an independent object. It is table-dependent and can only be maintained within a table.
You can enter the data type and number of places directly for a field. No data element is required in this case. Instead the data type and number of places is defined by specifying a direct type.
The data type attributes of a data element can also be defined by specifying a built-in type, where the data type and number of places is entered directly.
Two Level Domain Example
A domain defines a field technically and therefore it may
be used at different business levels.
A data element describes the meaning of a domain in a certain business context.
A domain, however, is used for the technical definition of a table field (for example field type and length).
Therefore, although a take-off airport (data element S_FROMAIRP) would have a different business meaning from an airport where a plane lands (data element S_TOAIRP), they could still have the same domain(here S_AIRPID) because technically we could assign the same number of characters whether the airport is a take-off or a landing airport.
Definitions of Table in Database
In SAP R/3 tables are defined as
A) Transparent tables: All of the fields of a dictionary table correspond to a field in the real database table.
B) Pooled tables: Different tables which are not linked to each other with a common key are combined into a TABLE POOL. Several logical tables thus exist as a single real database table.
C) Cluster tables: Several tables linked by a common key may sometimes be combined by the data dictionary and made to exist on the database schema as a single table.
SAP is evolving R/3 tables in transparent tables.
Elaboration on each of the definitions
A transparent table is automatically created on the database when it is activated in the ABAP Dictionary. At this time the database-independent description of the table in the ABAP Dictionary is translated into the language of the database system used.
The database table has the same name as the table in the ABAP Dictionary. The fields also have the same name in both the database and the ABAP Dictionary. The data types in the ABAP Dictionary are converted to the corresponding data types of the database system.
The order of the fields in the ABAP Dictionary can differ from the order of the fields on the database. This permits you to insert new fields without having to convert the table. When a new field is added, the adjustment is made by changing the database catalog (ALTER TABLE). The new field is added to the database table, whatever the position of the new field in the ABAP Dictionary.
Tables can also reside on the database as Pooled tables or cluster tables
Pooled Tables: Different tables which are not linked to each other with a common key can be combined into a Table Pool. The tables contained within this pool are called Pooled Tables. A table pool is stored in the database a simple table. The table's data sets contain, in separate fields, the actual key for the data set to be stored, the name of the pooled table and the contents of the data set to be stored.
Using this schema, several logical tables are combined into a single real database table. Although the data structure of each set is lost during the write to the table pool, it is restored during the read by the ABAP/4 Data Dictionary. The ABAP/4 Data Dictionary utilizes its meta-data to accomplish this.
Since information must be prepared (defined) within the ABAP/4 Data Dictionary when it is read or written to (or accessed), this process itself defines these as not transparent tables
Cluster Tables: Occasionally, several tables may be linked by a common key. The ABAP/4 Data Dictionary can also combine these tables into a single table. Each data set of the real table within the database contains a key and in a single data field, several data sets of the subsequent table for this key.
As mentioned above, these table types require special data handling, therefore they are not transparent tables.
Technical Settings in Dictionary
The data class logically defines the physical area of the database (for ORACLE the table space) in which your table should be created. If you choose the data class correctly, the table will automatically be created in the appropriate area on the database when it is activated in the ABAP Dictionary.
The most important data classes are master data, transaction data, organizational data and system data.
Master data is data that is rarely modified. An example of master data is the data of an address file, for example the name, address and telephone number.
Transaction data is data that is frequently modified. An example is the material stock of a warehouse, which can change after each purchase order.
Organizational data is data that is defined during customizing when the system is installed and that is rarely modified thereafter. The country keys are an example.
System data is data that the R/3 System itself needs. The program sources are an example.
Further data classes, called customer data classes (USER, USER1), are provided for customers. These should be used for customer developments. Special storage areas must be allocated in the database.
The size category describes the expected storage requirements for the table on the database.
An initial extent is reserved when a table is created on the database. The size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in the ABAP Dictionary.
You can choose a size category from 0 to 4. A fixed extent size, which depends on the database system used, is assigned to each category.
Correctly assigning a size category therefore ensures that you do not create a large number of small extents. It also prevents storage space from being wasted when creating extents that are too large.
Modifications to the entries of a table can be recorded and stored using logging.
To activate logging, the corresponding field must be selected in the technical settings. Logging, however, only will take place if the R/3 System was started with a profile containing parameter 'rec/client'. Only selecting the flag in the ABAP Dictionary is not sufficient to trigger logging.
Parameter 'rec/client' can have the following settings:
rec/client = ALL All clients should be logged.
rec/client = 000[...] Only the specified clients should be logged.
rec/client = OFF Logging is not enabled on this system.
The data modifications are logged independently of the update. The logs can be displayed with the Transaction Table History (SCU3).
Logging creates a 'bottleneck' in the system:
Additional write access for each modification to tables being logged.
This can result in lock situations although the users are accessing different application tables!
Create transparent table
Go to transaction SE11. Enter name of table you want to create (beginning with Y or Z) and click on create pushbutton
Enter the delivery class and the table maintenance criteria
The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems .
The display/maintenance indicator specifies whether it is possible to display/maintain a table/view using the maintenance tools Data Browser (transaction SE16) and table view maintenance (transactions SM30 and SM31).
Enter the name of the table field and the data element. The
System automatically populates the technical details for
existing data elements.
So far as possible it is advisable to use existing data elements which befit the business requirements.
However, we may create data elements if need be. The same is shown in the next slide.
To create a data element simply double click on it.
Alternately create a data element by simply choosing the
data type radio button on SE11 initial screen.
Create data element
The system prompts you to create a new data element.
Choose the Yes pushbutton.
Under the data type tab enter the domain name which
determines the technical characteristics of the field.
Further characteristics tab: Allows you to specify a search help assigned to the data element.
It also allows you to specify a parameter id which helps you populate a field from SAP memory.
Field label: Can be assigned as prefixed text to a screen field referring to the ABAP Dictionary. The text is displayed on the screen in the logon language of the user (if the text was translated into this language).
Create domain
If the domain does not exist in the data dictionary the
system prompts you to create one.
Give the technical characteristics under the definition
tab. Value range allows you value restriction at domain
level.
Value range tab:
As explained in the section Consistency through input checks one can restrict the possible values for a field at domain level itself by either entering fixed values or by specifying a value table under the tab Value range.
Currency/Quantity fields in a table
A currency or a quantity field must be assigned a reference field from a reference table containing applicable qty unit or currency unit.
Field of the reference table, containing the applicable quantity unit or currency
A field containing currency amounts (data type CURR) must be assigned a reference field including the currency key (data type CUKY).
A field containing quantity specifications (data type QUAN) must be assigned a reference field including the associated quantity unit (data type UNIT).
Create transparent table continue
Maintain the technical settings of the table by clicking on the tab

How to get the salesprice and condition for a customer / material / date

Hi all,
how can I get the correct price and condition for a customer / material / date ?
I know this is possible using the BAPI_SALESORDER_SIMULATE, but this bapi is using to much ressources on the system.
I'm trying to get the correct price and condition WITHOUT using that BAPI.
Does anyone know how it is possible ? As said before : I have the customer, material and a date.
thanks in advance for your help

Hi
You need it because it's possible to have a complex pricing procedure, and you can't do it with a simple select on a table. Think that you can have pricing requirements, formulas (ie: VOFM) and so on in your pricing procedure (tcode V/08).
I hope this helps you
Regards
Eduardo

Not able to create customer master data with country code US

Hey All,
I am not able to create customer master data in the Transaction Code XD01/FD01 with the country code as US.
The error message for the same is NO JURISDICTION CODE COULD BE DETERMINED. I have checked the tax code settings but could not locate the problem.
Request you to provide me with a solution.
Thanks & Regards
VK

Hey all,
I have checked the field in the account group(OBD2) but its in optional status
and also checked the country settings for US in the transaction code OY17 still the same error message, but when i tried checking the settings for a differnt company code's customer data base i can see that there is a number mentioned in the address tab under tax jurisdiction feild (beside time zone) which is not populating for this company code.
so, do anyone know where exaclty we mention this number so that it populates in that field of address.
hope am clear
hope to receive a solution
thanks & regards
vinila

What is the use for CREATING VIEW WITH CHECK OPTION?

Dear Legends,
I have a doubt
What is the use for creating view?
A: First Data Integrity, Selecting Particular Columns..
What is the use for creating a view with check option?
A: As per oracle manual I read that its a referential integrity check through views.
A: Enforcing constraints at DB level.
A: using CHECK OPTION we can do INSERTS UPDATES for a view for those columns who have no constraints... is it right??
A: If we do a INSERT OR UPDATE for columns who have constraints it will show error... is it right???
Please clear my doubt's Legends
Lots of Thanks....
Regards,
Karthik

Hi, Karthick,
karthiksingh_dba wrote:
... What is the use for creating view?
A: First Data Integrity, Selecting Particular Columns..Most views are created and used for convenience. A view is a saved query. If the same operations are often done, then it can be very convenient to code those operations once, in a view, and refer to the view rather than explicitly doing those operations.
Sometimes, views are created and used for security reasons. For example, you many want to allow some users to see only certain rows or certain columns of a table.
Views are necessary for INSTEAD OF triggers.
What is the use for creating a view with check option?
A: As per oracle manual I read that its a referential integrity check through views.The reason is integrity, not necessarily referential integrity. The CHECK option applies only when DML is done through the view. It prohibits certain changes. For example, if a user can't see certain rows through a view, the CHECK option keeps the user from creating such rows.
A: Enforcing constraints at DB level.I'm not sure what you mean. Please give an example.
A: using CHECK OPTION we can do INSERTS UPDATES for a view for those columns who have no constraints... is it right??No. Using CHECK OPTION, you can do some inserts and updates, but not others. The columns involved may or may not have constraints in either case.
A: If we do a INSERT OR UPDATE for columns who have constraints it will show error... is it right???If you try to violate a constraint, you'll get an error. That happens in views with or without the CHECK OPTION, and also in tables.

Steps to create customized Master data infoobjects in BI 7

Hi all,
Can anyone please send the detailed steps to create customized master data infoobject in BI7,and also the data is to be extracted from two different datasources from two different source systems.
Regards,
G.Monica Roja Flora.

Some data modelling tips while creating master data infoobject and extracting data from different source systems -
If there are identical characteristic values describing different objects for the same characteristic in various source systems, you have to convert the values in such a way in SAP BW so as to make them unique.
For example, the same customer number may describe different customers in different source systems.
You can carry out conversion in the transfer rules for this source system or in the transfer routine for the characteristic.
If work involved in conversion is too great, you can compound the characteristic to the InfoObject Source System ID (0SOURSYSTEM). This means it is automatically filled with master data. The Source System ID is a 2-character identifier for a source system or a group of source systems in BW. The source system ID is updated with the ID of the source systems that provides the data. Assigning the same ID to more than one source system creates a group of source systems. The master data is unique within each group of source systems.
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6399e07211d2acb80000e829fbfe/content.htm
Hope it Helps
Chetan
@CP..

Repository A2 is already used for document area DATAARCH (Data Archiving].

Dear ALL,
Actually I am getting probelem Photo configuration in back end.
I am using Transaction SM31 maitaining the table TOAAR_C, here I am getting probelem 'Content Repository Identification' (A2), here i am getting below error.
Repository A2 is already used for document area DATAARCH (Data Archiving].
Please look in to issue.
Regards,
venkat

Jürgen - your answer was very helpful and I'm sure I'm now in the right direction!
However I still have an issue:
When the write job is finished and before deleting and storage, the archive file is not accessible - and then I am not able to continue with deletion and storage.
An example:
Filename: RMM_EKKO11180104855_CLL
Logical path: ARCHIVE_GLOBAL_PATH_WITH_ARCHIVE_LINK
Physical file name: E:SAPContRepZ5RMM_EKKO11180104855_CLL
E:SAPContRepZ5 is the root of the content repository and should according to the documentation contain the file during the delete phase and until final storage in the repository. But there is no file there.
In the log of the write job there are the following entries:
Job started
Step 001 started (program RM06EW70, variant Z_DEMO_7, user ID CLL)
Reading purchasing documents
Archiving session 000913 is being created
Path:
Name for new archive file: RMM_EKKO11180104855_CLL
1 of 1 purchasing documents processed
Job finished
I am a little concern about that no path is written to the job log - could maybe mean something.
Any ideas?
Thanks,
Claus.

Regarding creation event in user exit for create customer

hi gurus,
in user exit how to create event for create customer
regards
vijay

Hi
Follow the below steps to find out what all BADI's are called when you press any button in any transaction.
1) Goto se24 (Display class cl_exithandler)
2) Double click on the method GET_INSTANCE.
3) Put a break point at Line no.25 (CASE sy-subrc).
Now
4) Execute SAP standard transaction
5) Press the required button for which you need to write an exit logic, the execution will stop at the break point.
6) Check the values of variable 'exit_name', it will give you the BADI name called at that time.
7) This way you will find all the BADIs called on click of any button in any transaction.
mark if helpful
Regs,
Tushar Mundlik

BTE's used for project systems master data.

Hi ,
Can anyone tell me what are the BTE's used for project systems master data.
Tcode used are CJ01, Cj02, CJ20N, CJ12, CNMASS
When master data is changed or created BTE should trigger.
Regards
Subin

I don't think there are any open_fi BTE available for PS master data.
you can use classic subs/vals using GGB0 and GGB1 transaction codes.

How to Create Customer Contact data in SAP CRM

Hi All,
Would want to create Customer Contact data in SAP CRM, could please guide me step by step that how can i create the customer contact data in SAP CRM?
Regards
Avinav

Hello Avinav,
In CRM 6.0 and 7.0 GUI is no more used, you can use WEB UI and login using SALESPRO role to create a contact.
1. Logon to CRM web UI
2. Choose Create Contact from the Navigation bar
3. Enter all the data - Title, first name, last name, account id,
street, stree2, street3, street4, street5, city, postal code, email,
mobile no and website.
4. Press the Save key.
Hope it will help! Please award points in case this helps!
Best Regards
Lata

Dual Control for Vendor/Customer Master Data

We can set Dual Control for Vendor/Customer Master Data. I have set it. According to the cycle, I have customized sensitive field, and make changes in Vendor/Customer A/c. Here the changes will be confirmed by other user who is authorised to confirm the changes. In this scenario, I would like to know, can we avoid this confirmation once we have actived? If, no than how could we confirm the changes and where can we set authorisation?

Dear,
No, You cannot avoid the dual check if You activate it. Another user by FK08 has to confirm the changes.
Then You can delete the field for the dual control into the table T055F and no check will be done in the future.
I hope this helps.
Mauri

BADi used for creating customer own data in transaction me52n

Similar Messages

Maybe you are looking for