Regarding dimension creation

Hi,
When I am creating a dimension it gives the default attributes like
ID-- surrogate Identifier
Name-- Business Identifier
Description Business Identifier
I have to create a dimension.
My dimension does not have these attributes.(ID,Name,Description).
Do I need to take all three default attributes or can I delete it.
I have to create 2 levels.
Is it necessary to take surrogate,Business Identifiers for each level.
Is it compulsary to add Surrogate Identifier for each level.
How can we decide the surrogate, Business Identifiers.
My dimension has 3 columns as a Primaykey.
It is urgent.
Please give me the suggestions.
Thanks,
Venkat

Hi Venkat
You do not need to define surrogate attributes. The slowly changing support in OWB needs surrogates, BUT you can model dimensions specifying just the business attributes (the level identifying attributes) and load the dimension table using a table operator in a map. Now I might be mixed up with all of my OWB versions but the wizard should allow you to delete/rename these attributes.
Cheers
David

Similar Messages

Is there any limit in Dimensions creation

Hi Friends, Ques :1 Is there any limit for dimensions creations in Essbase can we create more than 11 dimensions for exampls like a banking project.i want to the limit of dimensions creations? Ques: 2 Once we create a outline[dimesion & members] if client wants to add some more dimension then we create the additional dimension to the existing outline if yes then we add to delete all the data & freshly we had to load the data once again in the cubes. Pls help me friends by solving the above queries? Thanks & Regards 

Hi Syed, Ans1: Theoritically Yes. But if you go on increasing the dimensionsthe number of blocks(if the new dimension is sparse). the block size (if the new dimension is dense) may be theissues. If you are in planning application. there is a limit of 20dimesions.(6-system defined(Account, Entity,Scenario,Version,Timeand Period), 14 custom defined) Ans2: Once you create the outline and if client want to add adimension. you can do that. Whn you are adding new dimension itwill ask which member in new dimension you want to associate tehpresent data. hope this helps.

Problem regarding the creation of Table using CSS.

Hi ,
Here I have a Problem regarding the creation of Table using CSS.
In My Application i have a table with multiple rows(Rows are Dynamically added to the table).First i am setting the table with the following properties:
width:900px;
height : auto,
Overflow : visible,
Max-height: : 200px.
If I use above properties,I'm getting a table with 5 or 6 rows(height upto 200px).After that i am getting the Vertical ScrollBar.
The problem is when a table has many columns, Vertical and Horizontal Scrolls are coming at the time of setting the table. The table height is not Increasing dynamically.
How can i use "height" property in CSS? (I want the table height to be increased when the columns are more.)
Thanks & Regards
Madhavi

Hey humble user. Errr I'm trying to understand what ur trying to do. U want to create a section of a region destructively from an existing region right? If so select the option convert to new region (opt-comm-R or selecting it by right clicking). Check your audio bin to make sure. Whats the "merge" function? Are u refering to the glue tool?

Consolidation operators during Dimension creation

Hi everyone,
During dimension hierarchy creation, by default all Generations get default (+) addition as the consolidation operator.
How can I ignore(~) few members from consolidations at same or different generations ?
Thank you in advance

a detailed list of member property codes can be found in the online docs:
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/frameset.htm?dotrules.htm#dotrules1047244
you can not only influence the unary operator, but other attributes as well.
Hope this helps.
best regards
.T

Regarding Dimension Table and Fact table

Hello,
I am having basic doubts regarding the star schema.
Let me explain first regarding star schema.
Fact table containes Key fiigures and Dim IDs,Ok,
These DIm ids will be connected to my dimension tables.The Dimension table contains Characterstics and these Dim ids ,Ok.
Then My basic doubt
1.How does DIm id will be linked to SID tables
2.If I have not maintained any master data or text or Heirachies then SID tables will it be generated or not?
3.If it is generated I think there is use of This SID now..as we have not maintained Master data.
4.I am haing 18 characterstic which are no way related to each other in that scnerio how does Dimensions have to identified.?or we need to inclued whole chracterstics in one dimensions or we need to create seprate dimesnions for each of them..?(max is 13 dimensions)
5.If Dimension table contains dim ids and characterstics then where does the values for characterstics will be stored...?
( for ex..sales rep is characterstics for this we will be giving values some names where does these values will be stored..)

hi Vasu,
e.g we have infocube with
- dimension 'location' -> characteristic 'sales rep', 'country'
- dimension 'partner'.
fact table
dim-id('sales person') dim-id('partner') revenue
1001                   9001              500
1002                   9002              300
1003                   9004              200
dimenstion table 'location'
dim-id sid-id(sales rep) sid-id(country)
1001    3001              5001
1002    3004              5004
1003    3005              5001
'sales rep' sid table
sid   sales rep
3001 abc
3004 pqr
3005 xyz
'country' sid table
5001      country1
5004      country2
so from the link dim-id and sid, we get
"sales rep report"
sales-rep   revenue
abc        500
pqr        300
xyz        200
"country report"
country    revenue
country1   700
country2   300
hope it's clear.

Regarding Thread Creation

Hello,
To create a thread in java there are two methods.
(1) by extending from thread class.
(2) by implementing runnable interface.
implementing runnable interface is the preferred method to create a thread because we still have the option to extend from any other class.
But does anybody know why java provides 2 methods for thread creation, why doesn't it provide only option 2 (i.e. by implementing runnable interface) when it is the preferred option.
Regards,
Sandy.

Though Runnable interface is preferred to create threads in Java,most programmers extends Thread class.As jschell would say, 'I am rather certain' that the opposite is true.
The reason behind of this is that you can have a clear logic of your code by using ThreadThat's not even true and it certainly isn't a reason to extend Thread rather than implement Runnable.
most of the system programming written in java used Thread class instead of Runnable interface .If you have some evidence on the point please produce it. The consensus of opinion on these forums has been the other way round for many years.

Regarding equipment creation..

Hi Genius,
Now I want some details about Equipment creation in PM module, and what r all the table comes... please send some link to learn equipment creation.

hi thanus,
This is vijay here, currently i m working with this epm module.
for equipment creation you will use ie01 for change ie02 and for display ie03.
some times you may be asked to create by regarding doccument no.
then go to j3gi.
well main fields are equipment no, recipient, sender, planning plant, maintenance plant, bussiness area, company code etc.
there r lots of table.
but usefull are
equi,faglflaxa,j_3gbelp,j_3gbelk,iloa,ITOB,EQKTX,IMPTT,IMRG,CKBS,CKIS ETC
REGARDS
VIJAY DWIVEDI
REWARDS IF USEFULL*
FOR ANY FURTHER INFORMATION U CAN GET BACK TO ME

Regarding RFC creation

hi all,
after creation of RFC,we have to release the RFC or not.
regards,
subba reddy

Hi Subbareddy,
Yes you have to release the RFC after compeltion of creation.
After creation of RFC first import it into XI system and then test it once.If everything is working fine then you have to create a request for transporting this RFC from Dev system to QUALITY system.After creatiing the transport request then you can release the RFC with that transport request.With out releasing the RFC you can't move from Dev system to Quality system.
Plz close this post if you got the answer.
Regards,
Raju.

Regarding the creation of Webservice

Hi,
I have created a webservice and deployed sucessfully.
I would like to modify it and I deleted the Virtual Interface and the webservice definition.
After building the EJB module and EAR module, I cannot create the Webservice and the Virtual Interface.
I need help in tracing the problem.
Thanks and regards
Vivek

HI..
Two roles are provided for creating Web services:
● Web Service Developer
The Web service developer defines the Web service at design time. He or she knows the application logic as well as the resulting conditions for the communication type (for example, stateless/stateful), and the required security level. He or she defines these properties at an abstract level. Specific details, such as the transport binding or security concept to be used, are defined only later during the Web service configuration.
● Web Service Configurator
The Web service configurator defines the behavior of the Web service at runtime. He or she knows the system landscape and the technical requirements of the application server where the Web service is to be called. On the basis of the abstract definition of the Web service, the configurator can decide during configuration which specific attributes should be assigned to the features defined at design time.
Prerequisites
To create or consume Web services, you need the authorizations associated with the role SAP_BC_WEBSERVICE_ADMIN. You must add the authorization S_ICF_ADMIN (authorization for the Internet Communication Framework) to your profile. You use the authorization S_SERVICE for starting external services.
To create a Web service for a function module, function group, BAPI, or XI message interface with a predefined feature profile, use the Web Service Creation Wizard.
To specify the features of the Web service yourself, follow the procedure described in Creating a Virtual Interface.
You can also create Web services using the Web Service Creation Wizard, and then change the virtual interface and Web service definition in the Object Navigator (SE80), by choosing Enterprise Services ® Web Service Library.
for more Information click on the following link
http://help.sap.com/saphelp_nw04/helpdata/en/76/084e3ce0f9fe3fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/76/084e3ce0f9fe3fe10000000a114084/frameset.htm
Regards,
Arun

Regarding spool creation with 0 pages...

Hello,
I am using following code for spool creation but it gets created with 0 pages. Even though I can see data the spool has 0 pages due to which it causes issues when I try to convert spool to pdf.
DATA :
 lv_handle TYPE sy-tabix,
 lv_spoolid TYPE tsp01-rqident,
 lv_rc TYPE c,
 lv_errmessage TYPE c,
 et_table TYPE scarr OCCURS 0 WITH HEADER LINE.
SELECT *
FROM scarr
INTO TABLE et_table.
CALL FUNCTION 'RSPO_OPEN_SPOOLREQUEST'
EXPORTING
 dest = 'LP01'
IMPORTING
 handle = lv_handle
 spoolid = lv_spoolid
 rc = lv_rc
 errmessage = lv_errmessage.
LOOP AT et_table.
CALL FUNCTION 'RSPO_WRITE_SPOOLREQUEST'
 EXPORTING
 handle = lv_handle
 text = et_table-url
 IMPORTING
 rc = lv_rc
 errmessage = lv_errmessage.
ENDLOOP.
CALL FUNCTION 'RSPO_CLOSE_SPOOLREQUEST'
EXPORTING
 handle = lv_handle
IMPORTING
 rc = lv_rc
 errmessage = lv_errmessage.
DATA: v_pdf_bytecount TYPE i,
 it_pdf TYPE tlinetab.
" convert spool number to PDF
CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
EXPORTING
 src_spoolid = lv_spoolid
 no_dialog = ' '
IMPORTING
 pdf_bytecount = v_pdf_bytecount
TABLES
 pdf = it_pdf.
Please help.
Regards,
Jainam.
Edited by: Jainam Shah on Aug 26, 2009 5:53 PM
Edited by: Jainam Shah on Aug 26, 2009 5:53 PM
Edited by: Jainam Shah on Aug 26, 2009 6:07 PM

Solved by my own.
We need to use a FM as below to create page..
CALL FUNCTION 'RSPO_PAGE_BREAK_SPOOLREQUEST'
EXPORTING
 HANDLE = LV_HANDLE
OPTIONS =
LENGTH =
IMPORTING
RC =
ERRMESSAGE =
EXCEPTIONS
HANDLE_NOT_VALID = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.

Dimension creation in a cube

Hi friends,
what considrations should be takeen while creating a dimension in a infocube?. I want to know what type of cahrs to be included in one dimension to improve reporting performance and also the cube.
Can anyone please tell me or direct me to any documents.
Regards
Ananth.

Hi Ananth,
Here are few points to be considered while you model a cube
Create as many dimensions as possible.
Group similar objects in a dimension
Take care that the dimension table size does not exceed more than 20% of the fact table size.
Create a line item dimension for characterstics like sales document which have a very high granularity ratio.
Check the cardheight option while assigning the dimensions if there are relatively more number of objects in a dimension.
http://help.sap.com/saphelp_nw04/helpdata/en/fb/184538650fb10de10000009b38f842/content.htm
The above link is also much resourcefull.
regards

Regarding DC creation(DTR)

Hi all,
i am trying to create DC in the existing serevr track with the present DTR. But at the time of creation i am geting errors. They are;-
java.lang.reflect.InvocationTargetException
Create DC failed:
1) com.sap.tc.devconf.SyncException
2)Jul 21, 2008 11:51:31 AM com.sap.ide.eclipse.component.core.DCController [Threadmain,5,main] ERROR: Create DC failed: Unable to sync file or folder.: Sync for folder C:\Documents and Settings\JB67375\.dtc\1\SCs\sap.com\SAP_ESS\_comp\ failed: Communication error cause: Read timed out
Jul 21, 2008 11:51:25 AM com.tssap.dtr.client.lib.exceptions.ClientLibraryException [Threadmain,5,main] ERROR:
VFS version: 7.00 645_VAL_REL 0010 (2005-09-17 17:36:45 CEST) com.tssap.dtr.client.lib.vfs.VfsException: Sync for folder C:\Documents and Settings\JB67375\.dtc\1\SCs\sap.com\SAP_ESS\_comp\ failed: Communication error cause: Read timed out
Please help me out.
Regards,
Deepak

Hi Deepak,
Since the error is showing Read Timeout Error, can you just ping the DTR server from NWDS itself and check if the ping is successful or check the DTR URL..
Thanks
Namrata

Regarding Dimensions

Hi Experts,
Please tell me how to decide which charecteristic has to be inserted in which dimension.. Is there any criteria for that?
Immediate replies will help me a lot...
Advance Thanks & regards,
Chintu

First finalize the star schema model identifying fact table and its key figures (Ex: Revenue, Quantities etc) then decide the dimensions based on which the data is going to be sliced and diced (Dimension Ex: Customer, Product, Employee, Time etc). Then find out what are the various dimensional characteristics available in the source system. Based on that information now you may have to choose what are the various attributes you would like to keep inside the infocube for these dimensional characteristics and which are the attributes you would like to keep outside the cube as master data attributes of the characteristics in the dimensions. For example Material number, plant and store location can be inside the cube as characteristics and product hierarchy, text and other material related attributes can be outside the cube as master data attributes. Note use of master data attributes facilitates data loads and very dynamic as it can be resused with various cubes but it can slow down queries as it increases more table joins to read during query execution.
So as a developer you will have to choose the data model based on the user requirements, volume of data and number of dimension characteristics and their attributes and decide on where to keep what attributes either inside the cube or outside the cube.
Hope this helps please assign points if it does.
Thanks
A Ramasubbban

Problem regarding the creation of sales order using bapi.

Hai all,
I am creating sales order using bapi but i am, get following error messages :
TYPE ID NUMBER MESSAGE
E VP 112 Please enter sold-to party or ship-to party
E V4 219 Sales document was not changed
I have entered all the parameters.
my program is as follows :
*& Report ZSD_SALES_ORDER
REPORT ZSD_SALES_ORDER.
 Tables
*table definitions
TABLES:vbak, "Sales Document: Header Data
 knvv, "Customer Master Sales Data
 mara, "General Material Data
 t001l, "Plants/Branches
 mvke, "Sales Data for Material
 vbap, "Sales Document: Item Data
 konv. "Conditions (Transaction Data)
 Types
*type for upload data
TYPES :BEGIN OF ty_upload,
 matnr(20) TYPE c, " Old material number
 quantity(20) TYPE c, " Cumulative order quantity in sales units
VALUE TYPE BAPIKWERT1,
 value(20) TYPE c, " Condition value
 value TYPE konv-kwert, " Condition value
END OF ty_upload.
*type for final output table
TYPES :BEGIN OF ty_main,
 bismt TYPE mara-bismt, "Old material number
 matnr TYPE vbap-matnr, "Material Number
 kunnr TYPE vbak-kunnr, "customer number
 auart TYPE vbak-auart, "Sales Document Type
 vkorg TYPE vbak-vkorg, "Sales Organization
 vtweg TYPE vbak-vtweg, "Distribution Channel
 spart TYPE vbak-spart, "Division
 vbeln TYPE vbak-vbeln, "Sales document
 werks TYPE marc-werks, " Plant
 lgort TYPE mard-lgort, "Storage Location
 posnr TYPE vbap-posnr, "Sales Document Item
 parvw TYPE vbpa-parvw, "Partner function
 kwmeng TYPE vbap-kwmeng, "Cumulative order quantity in sales units
 kschl TYPE konv-kschl, "Condition type
 kwert TYPE konv-kwert, "Condition value
KWERT TYPE BAPIKWERT1,
 kwert(20) TYPE c, "Condition value
 waers TYPE konv-waers, "Currency
 END OF ty_main.
*type for old material number
TYPES: BEGIN OF ty_matnr,
 matnr TYPE mara-matnr,
 bismt TYPE mara-bismt,
 END OF ty_matnr.
*type for order number
TYPES :BEGIN OF ty_output,
 vbeln TYPE vbak-vbeln, "Sales Document
 END OF ty_output.
 Constants Begin with C_ *
CONSTANTS:
c_zpmu(4) TYPE c VALUE 'ZPMU',
c_zpmm(4) TYPE c VALUE 'ZPMM'.
DATA: c_ch(1) TYPE c VALUE 'X'.
 Data Begin with W_ *
*global data for validations
DATA: w_count TYPE i,
 w_vkorg TYPE vbak-vkorg,
 w_vtweg TYPE vbak-vtweg,
 w_spart TYPE vbak-spart,
 w_werks TYPE t001l-werks,
 w_check TYPE c,
 w_itemno TYPE posnr_va,
 W_COND TYPE C.
 w_cond(3) TYPE c.
 Internal tables Begin with IT_ *
*internal table definitions
DATA : it_upload TYPE STANDARD TABLE OF ty_upload ,
 wa_upload TYPE ty_upload.
DATA : it_main TYPE STANDARD TABLE OF ty_main,
 wa_main TYPE ty_main.
DATA: it_matnr TYPE STANDARD TABLE OF ty_matnr,
 wa_matnr TYPE ty_matnr.
DATA : it_output TYPE STANDARD TABLE OF ty_output.
Internal table for BAPI.
DATA: it_bapisdhd1 TYPE STANDARD TABLE OF bapisdhd1, "Sales and Distribution Document Header
 wa_bapisdhd1 TYPE bapisdhd1.
DATA: it_bapisditm TYPE STANDARD TABLE OF bapisditm , "Sales and Distribution Document Item
 wa_bapisditm TYPE bapisditm.
DATA: it_bapiparnr TYPE STANDARD TABLE OF bapiparnr, "SD Document Partner: WWW
 wa_bapiparnr TYPE bapiparnr.
DATA: it_bapischdl TYPE STANDARD TABLE OF bapischdl, "Schedule Lines
 wa_bapischdl TYPE bapischdl.
DATA: it_bapicond TYPE STANDARD TABLE OF bapicond, "Communication Fields for Maintaining Conditions in the Order
 wa_bapicond TYPE bapicond.
DATA: it_bapiret2 TYPE STANDARD TABLE OF bapiret2, "Return Parameter
 wa_bapiret2 TYPE bapiret2.
 Parameters Begin with PR_ *
*selection screen definition
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME .
PARAMETERS: pr_vkorg TYPE vbak-vkorg OBLIGATORY,
 pr_vtweg TYPE vbak-vtweg OBLIGATORY,
 pr_spart TYPE vbak-spart OBLIGATORY,
 pr_kunnr TYPE kna1-kunnr OBLIGATORY,
 pr_werks TYPE marc-werks OBLIGATORY,
 pr_lgort TYPE mard-lgort OBLIGATORY.
PARAMETERS: pr_auart TYPE vbak-auart OBLIGATORY,
 PR_AUGRU TYPE VBAK-AUGRU OBLIGATORY.
 pr_augru TYPE vbak-augru.
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME.
PARAMETERS : pr_file TYPE ibipparms-path OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk2.
 At selection-screen *
AT SELECTION-SCREEN.
PERFORM f006_validate_vkorg.
PERFORM f007_validate_vtweg.
PERFORM f008_validate_spart.
PERFORM f009_validate_kunnr.
PERFORM f010_validate_werks.
PERFORM f011_validate_lgort.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pr_file.
*for f4 help----
PERFORM f003_f4_help.
 S T A R T O F S E L E C T I O N *
START-OF-SELECTION.
*for material ,quantity and value upload
PERFORM f001_upload_file.
*get data
PERFORM f003_get_data.
*for check the data
PERFORM f002_check_data .
PERFORM f004_process.
*for posting
PERFORM f005_posting.
END-OF-SELECTION.
 E N D O F S E L E C T I O N *
*& Form f001_upload_file
 upload file
FORM f001_upload_file .
DATA : lw_fname TYPE string.
CLEAR lw_fname.
lw_fname = pr_file.
REFRESH it_upload.
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 filename = lw_fname
 filetype = 'ASC'
 has_field_separator = c_ch
 TABLES
 data_tab = it_upload
 EXCEPTIONS
 file_open_error = 1
 file_read_error = 2
 no_batch = 3
 gui_refuse_filetransfer = 4
 invalid_type = 5
 no_authority = 6
 unknown_error = 7
 bad_data_format = 8
 header_not_allowed = 9
 separator_not_allowed = 10
 header_too_long = 11
 unknown_dp_error = 12
 access_denied = 13
 dp_out_of_memory = 14
 disk_full = 15
 dp_timeout = 16
 OTHERS = 17.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT it_upload INTO wa_upload.
 wa_upload-value = ( wa_upload-value ) / 10.
 MODIFY it_upload FROM wa_upload.
ENDLOOP.
ENDFORM. "F001_UPLOAD_FILE
*& Form f003_f4_help
 f4 help
FORM f003_f4_help .
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 program_name = syst-cprog
 dynpro_number = syst-dynnr
 field_name = ' '
 IMPORTING
 file_name = pr_file.
ENDFORM. " f003_f4_help
*& Form check_data
 text
FORM f002_check_data .
DATA: lw_lines TYPE i.
DESCRIBE TABLE it_main LINES lw_lines.
IF lw_lines LE 0.
 RETURN.
ENDIF.
SELECT a~matnr
 a~bismt FROM mara AS a INNER JOIN mvke AS b
 ON amatnr = bmatnr
 INTO CORRESPONDING FIELDS OF TABLE it_matnr
 FOR ALL ENTRIES IN it_main
 WHERE a~bismt = it_main-bismt.
IF sy-subrc = 0.
 LOOP AT it_main INTO wa_main.
 CLEAR : wa_matnr.
 READ TABLE it_matnr INTO wa_matnr WITH KEY bismt = wa_main-bismt.
 IF sy-subrc = 0.
 MOVE: wa_matnr-matnr TO wa_main-matnr.
 ENDIF.
 MODIFY it_main FROM wa_main TRANSPORTING matnr WHERE bismt = wa_main-bismt.
 ENDLOOP.
ELSE.
 MESSAGE e000(zmsd) WITH text-001.
ENDIF.
ENDFORM. "CHECK_DATA
*& Form F009_validate_vkorg
 text
FORM f006_validate_vkorg .
CLEAR w_vkorg.
SELECT SINGLE vkorg
 INTO w_vkorg FROM tvko
 WHERE vkorg EQ pr_vkorg.
IF sy-subrc <> 0.
 MESSAGE e000(zmsd) WITH text-012 pr_vkorg.
ENDIF.
ENDFORM. " F009_validate_vkorg
*& Form f007_validate_vtweg
 text
FORM f007_validate_vtweg .
CLEAR:w_vtweg.
SELECT SINGLE vtweg
 INTO w_vtweg FROM tvtw
 WHERE vtweg EQ pr_vtweg.
IF sy-subrc <> 0.
 MESSAGE e089(zmsd).
ENDIF.
ENDFORM. " f007_validate_vtweg
*& Form f008_validate_spart
 text
FORM f008_validate_spart .
CLEAR:w_spart.
SELECT SINGLE spart
 INTO w_spart FROM tspa
 WHERE spart EQ pr_spart.
IF sy-subrc <> 0.
 MESSAGE e087(zmsd).
ENDIF.
ENDFORM. " f008_validate_spart
*& Form F010_validate_kunnr
 text
FORM f009_validate_kunnr .
DATA: l_kunnr TYPE kunnr.
CLEAR: w_vkorg, w_vtweg,w_spart.
SELECT SINGLE kunnr FROM knvv
 INTO l_kunnr
 WHERE kunnr = pr_kunnr
 AND vkorg = pr_vkorg
 AND vtweg = pr_vtweg
 AND spart = pr_spart.
IF sy-subrc <> 0.
 MESSAGE e000(zmsd) WITH text-010 pr_kunnr text-011 pr_vkorg .
ENDIF.
ENDFORM. " F010_validate_kunnr
*& Form f010_validate_werks
 text
FORM f010_validate_werks .
CLEAR:w_werks.
SELECT SINGLE werks
 INTO w_werks FROM t001w
 WHERE werks EQ pr_werks.
IF sy-subrc <> 0.
 MESSAGE e088(zmsd).
ENDIF.
ENDFORM. " f010_validate_werks
*& Form F011_validate_lgort
 text
FORM f011_validate_lgort .
CLEAR:w_werks .
SELECT SINGLE werks FROM t001l
 INTO w_werks
 WHERE werks = pr_werks
 AND lgort = pr_lgort.
IF sy-subrc <> 0.
 MESSAGE e000(zmsd) WITH text-007 pr_lgort text-008 pr_werks .
ENDIF.
ENDFORM. " F011_validate_lgort
*& Form f003_get_data
 text
FORM f003_get_data .
CLEAR wa_main.
REFRESH it_main.
LOOP AT it_upload INTO wa_upload.
 CLEAR : wa_main.
 MOVE: wa_upload-matnr TO wa_main-bismt,
 wa_upload-quantity TO wa_main-kwmeng,
 wa_upload-value TO wa_main-kwert,
 pr_vkorg TO wa_main-vkorg,
 pr_vtweg TO wa_main-vtweg,
 pr_spart TO wa_main-spart,
 pr_kunnr TO wa_main-kunnr,
 pr_werks TO wa_main-werks,
 pr_lgort TO wa_main-lgort.
 APPEND wa_main TO it_main.
ENDLOOP.
ENDFORM. " f003_get_data
*& Form f004_process
 text
FORM f004_process .
CLEAR w_check.
LOOP AT it_main INTO wa_main.
 IF wa_main-matnr = ''.
 WRITE:/ text-006,
 wa_main-bismt.
 w_check = 1.
 ENDIF.
 IF wa_main-kwmeng = 0.
 WRITE:/ text-005,
 wa_main-bismt.
 w_check = 1.
 ENDIF.
 IF pr_auart <> 'ZM01'.
 IF wa_main-kwert IS INITIAL.
 WRITE:/ text-004,
 wa_main-bismt.
 w_check = 1.
 ENDIF.
 ENDIF.
ENDLOOP.
ENDFORM. " f004_process
*& Form f005_posting
 text
FORM f005_posting .
CLEAR: w_itemno,
 w_cond.
w_itemno = 10.
w_cond = 1.
IF w_check = '' OR w_check = 1.
wa_bapisdhd1-doc_type = pr_auart.
wa_bapisdhd1-ord_reason = pr_augru.
LOOP AT it_main INTO wa_main.
 IF w_cond = 1.
 CLEAR: it_bapiret2,
 it_bapisditm,
 it_bapiparnr,
 it_bapischdl,
 it_bapicond.
 REFRESH:it_bapiret2,
 it_bapisditm,
 it_bapiparnr,
 it_bapischdl,
 it_bapicond.
 MOVE: wa_main-vkorg TO wa_bapisdhd1-sales_org,
 wa_main-vtweg TO wa_bapisdhd1-distr_chan,
 wa_main-spart TO wa_bapisdhd1-division.
 wa_bapisdhd1-wbs_eleM = 'Y561.1'.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
 EXPORTING
 INPUT = pr_kunnr
 IMPORTING
 OUTPUT = pr_kunnr.
 wa_bapisdhd1-PURCH_NO_S = pr_kunnr.
 wa_bapisdhd1-PURCH_NO_C = pr_kunnr.
 ENDIF.
 MOVE: w_itemno TO wa_bapisditm-itm_number,
 wa_main-matnr TO wa_bapisditm-material,
 wa_main-BISMT TO wa_bapisditm-material,
 wa_main-werks TO wa_bapisditm-plant,
 wa_main-lgort TO wa_bapisditm-store_loc.
 wa_bapisditm-target_qty = '10'.
 wa_bapisditm-PURCH_NO_S = pr_kunnr.
 wa_bapisditm-PURCH_NO_C = pr_kunnr.
 APPEND wa_bapisditm TO it_bapisditm.
 IF w_cond = 1.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-itm_number = 10.
 wa_bapiparnr-partn_role = 'SP'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 wa_bapiparnr-partn_role = 'AG'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 CLEAR wa_bapiparnr-partn_role.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-partn_role = 'RE'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 CLEAR wa_bapiparnr-partn_role.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-partn_role = 'RG'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 CLEAR wa_bapiparnr-partn_role.
 wa_bapiparnr-partn_numb = pr_kunnr.
 wa_bapiparnr-partn_role = 'WE'.
 APPEND wa_bapiparnr TO it_bapiparnr.
 ENDIF.
 wa_bapischdl-itm_number = w_itemno.
 wa_bapischdl-req_qty = wa_main-kwmeng.
 wa_bapischdl-PURCH_NO_S = pr_kunnr.
 APPEND wa_bapischdl TO it_bapischdl.
 wa_bapicond-itm_number = w_itemno.
 wa_bapicond-cond_type = 'ZECL'.
 IF ( wa_bapisdhd1-doc_type = 'ZPMU' ) OR ( wa_bapisdhd1-doc_type = 'ZPMM' ).
 wa_bapicond-cond_type = 'ZVAL'.
 ELSE.
 wa_bapicond-cond_type = 'ZMRP'. "+PK12122006
 ENDIF.
 wa_bapicond-cond_value = wa_main-kwert.
 APPEND wa_bapicond TO it_bapicond.
 w_itemno = w_itemno + 10.
 w_cond = w_cond + 1.
ENDLOOP.
data : SALESDOCUMENTIN like BAPIVBELN-VBELN.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
 EXPORTING
 order_header_in = wa_bapisdhd1
 IMPORTING
 salesdocument = SALESDOCUMENTIN
 TABLES
 return = it_bapiret2
 order_items_in = it_bapisditm
 order_partners = it_bapiparnr
 order_schedules_in = it_bapischdl
 order_conditions_in = it_bapicond.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_ch.
ENDIF.
LOOP AT it_bapiret2 INTO wa_bapiret2.
 DATA : w_err(100) TYPE c,
 w_matnr TYPE matnr.
 IF wa_bapiret2-type = 'E' AND wa_bapiret2-id = 'V1' AND wa_bapiret2-number = 392.
 UNPACK wa_bapiret2-message_v1 TO w_matnr.
 READ TABLE it_matnr INTO wa_matnr WITH KEY matnr = w_matnr.
 IF sy-subrc EQ 0.
 CONCATENATE text-013 wa_matnr-bismt INTO w_err SEPARATED BY space.
 MESSAGE w_err TYPE 'S'.
 ENDIF.
 ENDIF.
 IF WA_BAPIRET2-TYPE = 'S'. " Comment
 WRITE: 40 TEXT-009, WA_BAPIRET2-MESSAGE_V2+0(10).
 ENDIF.
ENDLOOP.
ENDFORM. " f005_posting
I have given all the necessary parameters. it is telling that error is in parameter
sales_header_in.
I have checked it.
i have assigned purch_no_s and purch_no_c of the structure BAPISDHD1(ORDER_HEADER_IN)
in the bapi with customer number.
and also i have assigned the partnumber of the structure BAPIPARNR ORDER_PARTNERS
in the bapi with customer number.
but still , it is diplaying the error message, please enter the sold to or ship to party number.
how to resolve this error.
this is urgent requirement.
points will be awarded.
thanking u in advance,
a.srinivas.

Hi,
Did u have a look at the standard programs which make use of BAPI_SALESORDER_CREATEFROMDAT1
Heres a list...
LWSSOU08
MV45WF0S
MWWMJF21_BAPI_SALESORDER_CREAT
RBUS2032
Regards,
Tanveer.
Please mark helpful answers

Regarding MIGO Creation

Hello,
While creating MIGO in Material Management, I'm getting this error " Account Determination for entry OPB0 (OPerational Chart of Accounts) BSX BPGC (Group Chart of Accounts) ____3000 not possible."
Please help me regarding this.
Thanks rin Advance,

Hi,
Please send the full error message along with the message number.
Regds
Aloysius

Regarding dimension creation

Similar Messages

Maybe you are looking for