Steps to create info Block

Dear All,
Anyone can tell me what are the steps to create info block and assign it to users.
Regards,
Ashima

Hi ,
How to create a new info block from sale summary and how to assign this new info block to a user.
Regards,
Ashima

Similar Messages

Steps to create info cubes

hi
can u plz let me know what r the steps to create info cubes and ods
and plz tell me stps to ods to info cubes
regards
sahsi

Hi Shashi,
Steps to create Infocube:
Go To InfoArea->Context Menu (right click)-> Select Create Info cube->Give Technical name & Description->Select the charactersitics , time characteristics and key figures you want in the cube from template->Create dimensions and make sure that all logically related characteristics are in one dimension-> Activate the infocube.
Steps to Create ODS:
Go To InfoArea->Context Menu (right click)-> Select Create ODS object->Give Technical name & Description->Select the characteristics which you want as key fields and drag & drop them in Key fields of ODS-> Select the key figures or characteristics which u want as data fields and and drag & drop them in data fields of ODS->Fianlly activate the ODS .
Regards,
Prakash B

Steps to create Info Packages in BI 7.0

Please Give Steps top create new Info packages in BI7.0

Hi,
Steps to create Generic data source:
If you want to extract the data from MM table in BI Please follow the below steps.
1) Create a view on that table By going in to se11( Do this for future purpose, no need of joining conditon as of now why because view is containing only one table at this juncture)
2) Go to RSO2, create generic data source based on view and designate this datasource under mm application component, it helps to replicate easily from the source system in BI side.
3) While Creating datasource make sure that field selections and selection criteria for fields.
4)Assign it to a package(specified by the team) for transportation purpose. Make sure the dependencies also will be going through request other wise the request may fail.
5) Replicate the generic datasource in BI System(by going in to the mm appln comp under r/3 source system)
6) After replication do create info package, transformations and dtp also.
7) Trigger the Info package and then DTP.
now data will be there in your data target in BI system
Steps to create standard data source
1> Go to RSA5 ,Select what data source u want , CLICK Transferstructure.
2> After dooing this u can see the structure in RSA6 , if u want to do any customozation by adding extra fields u can do it her , if not no need.
3> go to RSA3 and check if the structure is pulling data or not .
BW SIDE
4> Select Source system ->Replicate data source
5> create Transfer rules , update rules and cube and u are done
6> u can create a infopackage and schedule ur data load into the cube or ods.
Hope this helps you
Regards,
Rakesh

Create New Info Block in ECC for CRM Customer Fact Sheet

Hi,
we have a requirement to add a new info block in Customer Fact Sheet to display Equipment master from ECC. the info block required somehow is not listed in standard ECC info block.
is there any way i can configure the info block in ECC so i can call it from CRM? or do i need to develop it using ABAP in ECC?
thanks in advance

What I really really need is an example of how a new Assignment block can be created so that it appears in the PDF fact sheet.
I'm aware that the interface within the Smartform will need to be changed, along with the coding to process any new data being parsed in. The copied class, now called ZCL_UIU_PRN_ACCOUNT has a method called Collect_data which populates the itabs and forwards to the appropriate Smartform. I'm currently looking through this code to see what needs to be done.
The collect_data method loops through the data in the CRMT_BSP_PRINT table and retrieves the data structure and class, and I assume it calls them, but I have no idea what these classes have in common as I can't see common theme with them.
The data sources are:
CRMT_BSP_ACTIVITY2_BP
COMT_BSP_BP_ADDRESS
CRMT_BSP_CONTACT_OBJ_BP
CRMT_BSP_INT_HISTORY_BP
CRMT_BSP_OPPORTUNITY_BP
CRMT_BSP_ACC_R3_FACT_SHEET
CRMT_BSP_ACC_RELATION
CRMT_BSP_SALES_AREA_BP
and their associated class/interface is:
CL_BSP_ACC_ACCMOD_ACTIVITY
CL_BSP_BP_ACCMOD_ADDR_MIX
CL_BSP_ACC_ACCMOD_CONTACT
CL_BSP_ACC_ACCMOD_INT_HISTORY
CL_BSP_ACC_ACCMOD_OPPORTUNITY
CL_BSP_ACC_ACCMOD_PRN_R3DATA
CL_BSP_ACC_ACCMOD_RELATIONS
CL_BSP_ACC_ACCMOD_SALES_AREA
It would look like a lot of these classes are based on CL_BSP_*ACCMOD classes, but that's guesswork on my part.
I am unhappy that I seem to be pioneering here as there's no guide/help on exactly what needs to be done to add new AB's/sections to the PDF fact sheet. I find that strange as most areas are well documented, except this area as far as I know.
Sure, there is a note which identifies some of the objects that need to be changed, but misses out a vital table, but there are no guides. There are many people who produce videos on how to achieve the easier stuff, like adding fields to AB's via the UI configurator, but there seems to nothing in the area of extending the PDF fact sheet.
Jas
Edited by: Jason Stratham on Apr 29, 2010 10:22 AM

Steps to create Data loading from Flat File to Info Cube in BI

Hi,
     I am very new BW, I need some one help. When I am trying to create info source i am any pop window stating to create Transaction data or master data.
     After creating Info source, I dont know how to assign this info source to source system (which i created).
      When select the context menu of info source I dont have option to assign the datasource.
      And one more thing is When I am creating the Info Cube. I cant understand how to create.
      Please some one help me how to map the fields to Source system.
Regds
Dave.

Hi,
For flat file upload, first you need to create the source system.
Then you need to create the infosource based on the format of the flat file you are going to upload or vice versa depending on your requirements.
Once your infosource is ready, right click on it and select assign datasource. Here you can assign your flat file datasource. Then create an infopackage and give the path from where the file is to be upload to BW (in the infopackage).
Also look at the thread below for procedure on flat file upload :
http://help.sap.com/saphelp_nw04s/helpdata/en/8e/dbe92341c84242be2c7d3917f1c197/frameset.htm
Cheers,
Kedar

Add new info block in Tcode VC/2

Hello All,
Could someone guide me how to add new intoblock in tcode VC/2.
Currently SAP provide 22 info blocks. I need to add new infoblock
This is what I do.
Go to tcode VC/2 enter information and execute . Click on infoblock this will give list of available infoblocks. Please let me know can we modify these infoblock . or can we add new.
Regards,
Vinod Gilbert

Hi,
Create the fact sheet views that you want to include in the component workbench.
Under UI framework def>factsheet> assign these views to a fact sheet.
Then these views are then displayed in Available Fact Sheet Views in the fact sheet configuration using bsp_dlc_fs component within the component workbench.
Select the created view as one of the tile in factsheet.
Hope this helps
Srinivas

Steps to create tabstrip for subscreen in selection screen

hi,
can let me know the steps taken to create subscreen in selection screen and put in tabstrip?
i need to have 3 screens. 1000 being the tabstrip, 2000 being first subscreen and 3000 being the second subscreen.
i have the abap code but i do not know the steps to create especially 1000 screen.
for 2000 and 3000, once i activated the program, these 2 screens added but i do not know where can i create the 1000 screen.
also, should i use wizard to create tabstrip?
please advise. thanks
SELECTION-SCREEN BEGIN OF SCREEN 2000 AS SUBSCREEN.        SELECTION-SCREEN BEGIN OF BLOCK x WITH FRAME TITLE text-001.
SELECT-OPTIONS: para1 FOR field1 ,
                              para2 FOR field2.
SELECTION-SCREEN END OF BLOCK x.
SELECTION-SCREEN END OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF SCREEN 3000 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK y WITH FRAME TITLE text-002.
SELECT-OPTIONS: para3 FOR field3 ,
                              para4 FOR field4.
SELECTION-SCREEN END OF BLOCK y.
SELECTION-SCREEN:SKIP.
SELECTION-SCREEN END OF SCREEN 3000.

e_l,
See the total doc.. with example.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
                  <area2> INCLUDING [<prog 2>] <dynp 2>,
                  <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
                  <area2>,
                  <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
                  SUB2 INCLUDING SY-REPID '0120',
                  SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
                  SUB2,
                  SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ELSE.
    MYTABSTRIP-ACTIVETAB = SAVE_OK.
    CASE SAVE_OK.
      WHEN 'PUSH1'.
        NUMBER = '0110'.
      WHEN 'PUSH2'.
        NUMBER = '0120'.
      WHEN 'PUSH3'.
        NUMBER = '0130'.
    ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control
Pls. reward if useful

LSMW creating info records

I am using standard batch input LSMW for creating info records with obj 0060 and program RM06IBI0. In the last step while running session I am getting error as 'Field EINE-EVERS. (shipping instructions ) is not an input field.' Does anybody know why? Is this field not there in ME11 transaction?

resolved

Creating info records ME11 LSMW

I am using standard batch input LSMW for creating info records with obj 0060 and program RM06IBI0. In the last step while running session I am getting error as 'Field EINE-EVERS. (shipping instructions ) is not an input field.' Does anybody know why? Is this field not there in ME11 transaction?

resolved

STEPS TO CREATE A MEMBER FOR LOYALTY PROGRAM

Hi ,
I am currently trying to set all the necessary steps to create a simple scenario in order to understand the functionality of loyalty. Until now, I have created a loyalty program, a RewardRule Group and a RewardRule, However, i don´t know which steps should i follow to create and assign a member into a loyalty program.
1. Obviously, I have to create the member first, but, if I need to use a private account that already exist, to be assigned as a member, should I enter a specific role in the assigment role block inside the private account ?.A consultant told me that we have to use the role u201CMemberu201D, but this role doesn´t exist in our sytem
2. Once the member has been created, should i assign it into a membership , using the member ID created in the previous step?.
3.Other steps?
Thanks, and waiting for any help
DPL

Hello,
As far as I am aware, a member is just a standard individual/corporate account and Membership represents the participation of an individual account (natural person) in a loyalty program. I don't think any additional role needs to be maintained for a member to be added to a membership. If you want to create a new member, it would be equivalent to creating a new account.
So the step should be to just create a membership and during creation, from the F4 help, you can choose the account you want to assign to this membership and also the Loyalty Program can be chosen from the DDLB.
There are different types of membership available such as Standard Membership , Shared Account Membership
Group Membership for which you can go through the documentation in SMP or help.sap.com.
Hope this helps.
Regards,
Nisha

Steps to create Universe from Microsoft SQL oder Oracle Database

Hi All,
i am looking for a document which describe the steps to create an Universe base on Microsoft SQL oder oracle database.
Thank you in advance
Pat

Hi,
These links may be help for you:
http://www.bidw.org/business-objects/universe-design/getting-started-with-universe-design/
http://www.sap-businessobjects.info/universe-design.htm
All the Best,
Madhu...

Steps to create Numer range buffering

Hi Gurus,
Can any b'dy explain the concept of number range buffering and also i need steps to create number range buffering for transactional data.
here we have a full load it has to load 50L of records daily . it is taking 1.5 hr to 2 hr to load this data into an info cube we are looking to improve this load performence.
thanks in advancde to all gurus.
lax

hi,
Welcome to SDN...
basically number range buffering is used to increase performance. usualy SID number range buffered,
transaction rsrv can be used to check -> all elementary tests >> master data >> compare number range and max sid. and >> transcation data >> comparison of rumber range and max dimid.
transaction SNRO is used to maintain number range.
http://help.sap.com/saphelp_nw04/helpdata/en/7b/6eb2aa7aed44ea92ebb969e03081fb/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/95/3d5540b8cdcd01e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/aa/dbc9b4b56143bb8f2ae909d7d040fa/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/71efb490-0201-0010-949b-b2344b58b094
Number Range Buffering can help cube loads if you your loads result in a good number of new Dim IDs being created with the load.
Without buffering, each row of data to be loaded that would require a new Dim ID to be assigned (because it is new combination of characteristics for that dimension) must go out and read the Number Range table for that specific Dimension and get the next available number. So if you add 50,000 rows to a cube that results in 5,000 new Dim IDs to be assigned, that means 5,000 queries that must go read the table. Now if you buffered 500 numbers at a time, that would mean only 10 queries to the number range table.
In a perfect BW world, someone in your shop would have the ability to go to your P system and make the change. Chances are, this ability is locked down and you will have to get the P opened to make the change.
This can also make a big improvement in the load time if you are doing a large initial load of millions of rows to a cube.
FOR MORE DETAILS http://www.sap-img.com/ge003.htm
Re: SMS through SAP
pls assign points if useful..
-Shreya

Steps to create outbound CREMAS IDOC from ERP

Hi,
Can you please share the steps to create outbound IDOC from ERP system?
Business requirement is that whenever a new vendor is created in the ECC system, SAP should trigger an outbound vendor IDOC CREMAS from ERP system. Also whenever the vendor data is changed then the entire vendor details should be passed to outbound IDOC and not just the delta changes. Change pointer can be configured but to create idoc for full vendor records.
I guess we can use CREMAS.
Can anyone please share the steps to configure it in ERP?
Regards,
Sandeep

1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
    TABLES
      IDOC_CONTROL       = i_edidc
      IDOC_DATA          = i_edid4.
a®

New Info Block in BP Fact Sheet

Hi Experts,
How i can add new Info Block to Business Partner Fact Sheet (BP_FACTSHEET) with other class and all data.
I will write some ABAP program with data but how i can assing it to new info block?
Any ideas?
Thanks to all

Hi,
Create the fact sheet views that you want to include in the component workbench.
Under UI framework def>factsheet> assign these views to a fact sheet.
Then these views are then displayed in Available Fact Sheet Views in the fact sheet configuration using bsp_dlc_fs component within the component workbench.
Select the created view as one of the tile in factsheet.
Hope this helps
Srinivas

STEPS for creating IDOC .

I need to creat IDOC for whenever delivery is created .

Hi
Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use
see the doc
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
>>>> SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
<b>Reward points for useful Answers</b>
Regards
Anji

Steps to create info Block

Similar Messages

Maybe you are looking for