Any tutorial for creating a business object type in the BOR ?

Hello,
I want to create an object in the BOR, can you please pin point good tutorial to follow explaining how to create a business object type.
Points are awarded
Regards

Hi
Refer to the following links
http://help.sap.com/saphelp_47x200/helpdata/en/a5/3ec8074ac011d1894e0000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/7c/3ce3b465ba11d395fe00a0c94260a5/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/3ec8724ac011d1894e0000e829fbbd/frameset.htm
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Similar Messages

Business Object Type

I needed to associate a document with a business object type.
The transaction is ME41. I was only able to associate the document
with a business object by bringing up a document, creating a file
attachment, and then looking into table srgbtbrel and seeing that the
business object was BUS2010.
Is there an easier way to do something like this for other document types?

I think this is the best way.

How to access Business object type attribute from a method/function modul ?

Hello,
i have created a business object type object along with attributes and methods. Now inside the method i want to access the attributes. inside the method i am writing:
data a type XXX.
a = me->attribute
this is creating a compilation error.
Now the method is defined as a function module in some package, so can anyone inform me how to access object attributes from the function module ?
pointes are awarded
Regards

Hello,
thanks for your answer, but this too did not work, "=>" is for static attributes and the attributes i have are not static. Moreover, i tried it but it gave the same error :
the abap error was when i was checking the code is :
the type me=>documenttype is unknown
as you know in SWO1 i created an object and when i create a method you link it to a function module and this is where you have the implementation of the method, so from this method how can i access the attributes on the main object that i created in SWO1
regards

Creating a Business Object

Hi,
I would like to know the Step by Step procedure for creating a business object.
My requirement is to create a new business object and use it in my Workflow.
If any material is available please forward to my Email ID.
Mail ID : [email protected]
Thank you,
Ramu N.

Hi Ramu,
Why dont you refer the following link
http://help.sap.com/saphelp_nw2004s/helpdata/en/4f/5668735cf211d194a30000e82dec10/frameset.htm
Regards,
Raja Sekhar

Business object type for parked invoices

Hi,
We are using documentum to store documents that have been attached to business object types in SAP. The business object types are configured in transaction OAC3 to point to a pre-configured content repository.
Having this configuration allows the object type to use the "services for objects" option, enabling it to store attachments.
The business object types for invoices have been configured and we are able to store attachments. However this does not seem to work for "Parked invoices". The configuration in the "services for objects" component is not there and the feature to store the attachment is disabled.
As the configuration needs to be done for all object types that need to be able to store attachments, maybe someone here can indicate what the object type is for parked invoices. Alternatively, maybe there is a way to look up the various business object types.
Any help you can provide is appreciated.
Thanks.
Kind Regards,
Giwan

Hi ,
Thank You for your reply.
I created inquiry . it takes BUS2031.But BUS2031 is used for quotation.But that inquiry is open in VA12(Change Inquiry) Transaction,not open in VA22(Change Quotation).
Is there any setting for BOR object types to Document Types.
Please give me a reply as early as possible.It's very urgent.
Thanks,
Saritha

Create a business object for a Maintenance object

Hello,
I want to create a business object for a maintenance object to change all XML attributes to XML elements.
Should I have to change the whole XML Schema from attributes to elements one by one?
For example, I create the business object CM_Person_BO for the maintenance object Person, and use the business object to add user in a more standard way.
But it is a quite large job to rewrite the whole schema for the maintenance object Person, which has following elements, which are PersonIdentifiers, PersonNames, PersonPhones, PersonCharacteristics, Person and SeasAddress.
Is there any easy way to do it?
Thanks,
Kerr

Should I have to change the whole XML Schema from attributes to elements one by one?
Is there any easy way to do it?Unfortunately not, you will have to define the schema containing each field/element, once. The primary objective is that you should create a scaled down version of the BO having only the required fields or subset of available fields, you may not need all the fields of a MO. This increases performance as the IO is performed only for specified fields in the BO.
You can define separate Data Areas for each Person object's context, i.e. Identifiers, Names, Phones, etc. and include them (includeDA) within the Person BO (CM_Person_BO) for clarity.

Business Object Types for Z-tables

hi
could anyone please guide me how to create business-object-types for Z-tables?
thanks in advance
regards
pavan

Hi,
Business objects (SWO1) are representations of business entities.
So it is impossible to ask I need to create a business object for a z-table, because that's not business specific.
Normally when you're faced with a BO issue, you first search for useable existing BO's. In there you also search if SAP has already provided the wanted functional requirement. If this is not present, you then search for a BO which is closest to the Functional requirement and then create a subtype of that BO en extend it to suit your needs (attributes, methods, events etc.) via delegation you can then also se it in sap standard.
for more infor check the SAP Business Workflow

Transaction KB16N business-object type and key for GOS

When attachments (notes, PC documents etc) are made to a manual cost allocation in transaction KB16N using GOS (generic object services):
what is the business-object type?
how is the business-object key constructed?
I suspect that the business-object type is BUS6036.
I suspect that the business-object key is the concatenation of the controlling area and the document number (using internal values).
Is that correct?
The reason for my question is that I have a program to display attached notes (and allow drill-down to attached PC documents) that works for various business objects (billing documents, purchasing documents and some FI documents), but I cannot get it to work for manual cost allocations.
John

Hi Michele
The transaction you are looking for should be SWO1
Then put the ex "BUS2000116" into the Object/Interface type and ...
Guess it will help you
Best Regards
Daniel

Are there any shortcuts for creating Value Object Classes?

Hi,
I'm using a Remote Object to connect to my server
(pyAMF/Django). I'm getting stuck with the creation of Value Object
Classes. It doesn't seem very DRY to have a class on my server
representing the data model and then have to recreate that class
and all its properties in my Flex app.
Are there any shortcuts for creating client side VOs from
server side data?
I was thinking about declaring an empty VO class in Flex, and
then dynamically assigning/casting my Proxy object to that class.
It seems like that approach may cause problems for the Flex
compiler though.
Any hints?
Thanks!

quote:
Originally posted by:
tptackab
Oh man, do I feel your pain. I'm not sure what middle-tier
technology you're using, but I'm using Java (w/Spring) and I
absolutely hate having to create and maintain two sets of VO (aka
data transfer - DTO) object for Java and Flex.
One thing that has helped me in that area is a free tool from
Farata Systems called
DTO2Fx. If you're using Java and Eclipse, it's a great time saver.
You simply install a (very lightweight) Eclipse plugin, add a
single annotation to your Java VO classes, and it automatically
generates your Flex VOs. It even creates a base and extended
version of each VO on the AS3 side so you can add code to the
extended VO without fear of having your changes overwritten when it
regenerates your Flex VOs.
Here's a like to thier
PDF that
gives instructions and a download link. I had it up and running in
my application in less than 30 minutes!
I'm using Python/Django serverside (PYAMF is my AMF
serializer).

Unix: Any support for creating com objects?

I'm looking into migrating a CF 8 server from Windows to
Unix. I see in the documentation for CreateObject that com objects
are not supported on Unix, "Note: On UNIX, this function does not
support COM objects."
Obviously, this won't work on Unix: Note:
<cfset image = CreateObject( 'com', 'ImageStoreCom.Image'
)>
But what about this, can I create a remote com object?:

<cfset image = CreateObject( 'com',
'ImageStoreCom.Image', 'remote', '172.0.0.1' )
Finally, if the example above is out of the question, are
then any techniques for exposing a com object to CF on a Unix box?
I'm wondering if maybe I could write a Java wrapper for the com
object and expose it that way?
Thanks for your help,
DJ

<ShotInTheDark>You might try wrapping your COM object
in a .NET class then accessing your .NET class
remotely.</ShotInTheDark>
http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=dotNet_02.html#1160020

Are there any bapi for create Business Partner

Dear Sir,
Do you know are there any bapi for create Business Partner in CRM
Please advise.
Thank you and best ergards,
Vimol

Dear Vimol,
BAPI_BUPA_CREATE_FROM_DATA ......SAP BP, BAPI: Create Business Partner
BAPI_BUPA_FS_CREATE_FROM_DATA .......SAP BP, BAPI: Create Business Partner
BAPI_BUPA_FS_CREATE_FROM_DATA2 .......SAP BP, BAPI: Create Business Partner
Hope this will help.
Regards,
Naveen.

Someone has a tutorial for creating screen exit?

I have a development and I do not know how to create screen exit.
Case Someone has a tutorial for creating screen exit please help me
Thank you
Wagner Duarte
Consultant - SAP ABAP

hI
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
Have a look at below link It will definately help you to undestand the same.
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
check these links.
http://help.sap.com/saphelp_46c/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/screen_exit.html
USER EXITS
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
1. Go to the screen>System>Status-->Program (Double
click this program. It will take you to the program.
2. Now, Goto-->Object Directory Entry.
3. Make a note the package name.
4. Now run the transactions SMOD, press F4 and enter the
above noted package, press enter.
5. It will display list of Exits.
6. Now go back to the initial screen SMOD.
7. Specify the exit name here and select the radio button
Components.
8. It will display four group boxes one for FM, second
for Fcodes, thrid for Screen areas and last for
includes.
9. Goto transaction CMOD, create a new project, and
click the button "Enhancement assignments" and
specify your enhancements that you got in SMOD.
10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
and you just go through these links also
Screen exit
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
screen-exits
Check the following link.
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all

Delete Business Object Type (SWO1)

Hi gurus,
How can we delete/modify objects in SWO1 that were created in a previous version. Are these actions allowed, is there a workaround if its not allowed?
Thanks for your help!
Jason

Hi Raymond,
Thank you for your help.
I have come accross that thread in SDN while doing some research already. But It does not completely answer my question.
Correct me if I'm wrong, this means there is absolutely no workaround to modify a business object type that has been created in a different version? If thats the case why does SAP enforce this rule?
Thank you

Can i Create A business object of my own without inheriting

hi gurus,
Can i Create A business object of my own without inheriting from any other business object. i Know how to create sub type.

yes, u can choose 'create' button in SWO1 and not fill field Supertype.
or copy your new BO from already exist.

Maximum Numbers of profiles that can be created in Business Objects CMC??

Hi,
I want to know if there exists any limitation in the number of profiles that could be created in Business Objects Enterprise CMC. My question is because I need to restrict the reports that users can see in the InfoView and a way to do this is creating a profile for each customer for example. I want to create 5000 profiles approximately
Thanks a lot

Hi,
i never heared of a limitation there. Even in your size.
If you need an official Answer i would recommend creating an OSS Message at SAP.
Regards
-Seb.

Any tutorial for creating a business object type in the BOR ?

Similar Messages

Maybe you are looking for