LSMW FOR UPLOADING INFO RECORD-ME11 USING RECODING METHOD
Hi Guys,
I am uploading inforecords using LSMW recording method.
While recording I entered net price and other things properly.
When I am running the lsmw, net price filed becoming gray(Non editable) filed and system shows error as "it is not an input filed". But if i try to execute the t-code sepeartely this filed is in editable mode.
Please let me know what is the priblem.
Thanks
Dhanu
Hi Dhanu,
there is the easiest method to do that you can follow the Direct input method the object for info record id 0060 and program is RM06IBI0,
With this method you will not get any problems. it is SAP recommended method.
Bhima
Similar Messages
-
Uploading info records by using BDC
Hi all,
Does any one having knowledge in uploading info records (ME11) by using BDC.
Problem arises when going for multiple scales.
Can any one let me know how proceed this BDC.
Regards,
RajGoto transaction SHBD enter a recording name and specify the transaction code.
Enter the test data and save it , it will actomatically create a bdc program.
now select that recording name and click create program icon and specify the program name.
This is the program which was created using transaction SHDB for XD01.
include bdcrecx1.
parameters: dataset(132) lower case.
DO NOT CHANGE - the generated data section - DO NOT CHANGE ***
If it is nessesary to change the data section use the rules:
1.) Each definition of a field exists of two lines
2.) The first line shows exactly the comment
'* data element: ' followed with the data element
which describes the field.
If you don't have a data element use the
comment without a data element name
3.) The second line shows the fieldname of the
structure, the fieldname must consist of
a fieldname and optional the character '_' and
three numbers and the field length in brackets
4.) Each field must be type C.
Generated data section with specific formatting - DO NOT CHANGE ***
data: begin of record,
data element: KUN16
KUNNR_001(016),
data element: BUKRS
BUKRS_002(004),
data element: VKORG
VKORG_003(004),
data element: VTWEG
VTWEG_004(002),
data element: SPART
SPART_005(002),
data element: KTOKD
KTOKD_006(004),
data element: ANRED
ANRED_007(015),
data element: NAME1_GP
NAME1_008(035),
data element: SORTL
SORTL_009(010),
data element: NAME2_GP
NAME2_010(035),
data element: STRAS_GP
STRAS_011(035),
data element: PFACH
PFACH_012(010),
data element: ORT01_GP
ORT01_013(035),
data element: PSTLZ
PSTLZ_014(010),
data element: ORT02_GP
ORT02_015(035),
data element: PFORT_GP
PFORT_016(035),
data element: PSTL2
PSTL2_017(010),
data element: LAND1_GP
LAND1_018(003),
data element: REGIO
REGIO_019(003),
data element: SPRAS
SPRAS_020(002),
data element: TELX1
TELX1_021(030),
data element: TELF1
TELF1_022(016),
data element: TELFX
TELFX_023(031),
data element: TELF2
TELF2_024(016),
data element: TELTX
TELTX_025(030),
data element: TELBX
TELBX_026(015),
data element: URL
KNURL_027(132),
data element: STCD1
STCD1_028(016),
data element: STCD2
STCD2_029(011),
data element: BBBNR
BBBNR_030(007),
data element: BBSNR
BBSNR_031(005),
data element: BUBKZ
BUBKZ_032(001),
data element: BRSCH
BRSCH_033(004),
data element: LZONE
LZONE_034(010),
data element: KUKLA
KUKLA_035(002),
data element: BRSCH
BRSCH_036(004),
data element: UMSA1
UMSA1_037(020),
data element: UWAER
UWAER_038(005),
data element: UMJAH
UMJAH_039(004),
data element: JMZAH
JMZAH_040(006),
data element: JMJAH
JMJAH_041(004),
data element: BANKS
BANKS_01_042(003),
data element: BANKK
BANKL_01_043(015),
data element: BANKN
BANKN_01_044(018),
data element: ABLAD
ABLAD_01_045(025),
data element: KNKAL
KNFAK_01_046(002),
data element: CIVVE
CIVVE_047(001),
data element: ANRED_AP
ANRED_01_048(030),
data element: ANRED_AP
ANRED_02_049(030),
data element: NAMEV_VP
NAMEV_01_050(035),
data element: NAMEV_VP
NAMEV_02_051(035),
data element: NAME1_GP
NAME1_01_052(035),
data element: NAME1_GP
NAME1_02_053(035),
data element: TELF1
TELF1_01_054(016),
data element: TELF1
TELF1_02_055(016),
data element: ABTNR_PA
ABTNR_01_056(004),
data element: ABTNR_PA
ABTNR_02_057(004),
data element: AKONT
AKONT_058(010),
data element: DZTERM
ZTERM_059(004),
data element: MAHNA
MAHNA_060(004),
data element: BZIRK
BZIRK_061(006),
data element: AWAHR
AWAHR_062(003),
data element: WAERS_V02D
WAERS_063(005),
data element: KALKS
KALKS_064(001),
data element: LPRIO
LPRIO_065(002),
data element: KZAZU_D
KZAZU_066(001),
data element: ANTLF
ANTLF_067(001),
data element: PERFK
PERFK_068(002),
end of record.
End generated data section ***
start-of-selection.
perform open_dataset using dataset.
perform open_group.
do.
read dataset dataset into record.
if sy-subrc <> 0. exit. endif.
perform bdc_dynpro using 'SAPMF02D' '0100'.
perform bdc_field using 'BDC_CURSOR'
'RF02D-KTOKD'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RF02D-KUNNR'
record-KUNNR_001.
perform bdc_field using 'RF02D-BUKRS'
record-BUKRS_002.
perform bdc_field using 'RF02D-VKORG'
record-VKORG_003.
perform bdc_field using 'RF02D-VTWEG'
record-VTWEG_004.
perform bdc_field using 'RF02D-SPART'
record-SPART_005.
perform bdc_field using 'RF02D-KTOKD'
record-KTOKD_006.
perform bdc_dynpro using 'SAPMF02D' '0110'.
perform bdc_field using 'BDC_CURSOR'
'KNA1-KNURL'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNA1-ANRED'
record-ANRED_007.
perform bdc_field using 'KNA1-NAME1'
record-NAME1_008.
perform bdc_field using 'KNA1-SORTL'
record-SORTL_009.
perform bdc_field using 'KNA1-NAME2'
record-NAME2_010.
perform bdc_field using 'KNA1-STRAS'
record-STRAS_011.
perform bdc_field using 'KNA1-PFACH'
record-PFACH_012.
perform bdc_field using 'KNA1-ORT01'
record-ORT01_013.
perform bdc_field using 'KNA1-PSTLZ'
record-PSTLZ_014.
perform bdc_field using 'KNA1-ORT02'
record-ORT02_015.
perform bdc_field using 'KNA1-PFORT'
record-PFORT_016.
perform bdc_field using 'KNA1-PSTL2'
record-PSTL2_017.
perform bdc_field using 'KNA1-LAND1'
record-LAND1_018.
perform bdc_field using 'KNA1-REGIO'
record-REGIO_019.
perform bdc_field using 'KNA1-SPRAS'
record-SPRAS_020.
perform bdc_field using 'KNA1-TELX1'
record-TELX1_021.
perform bdc_field using 'KNA1-TELF1'
record-TELF1_022.
perform bdc_field using 'KNA1-TELFX'
record-TELFX_023.
perform bdc_field using 'KNA1-TELF2'
record-TELF2_024.
perform bdc_field using 'KNA1-TELTX'
record-TELTX_025.
perform bdc_field using 'KNA1-TELBX'
record-TELBX_026.
perform bdc_field using 'KNA1-KNURL'
record-KNURL_027.
perform bdc_dynpro using 'SAPMF02D' '0120'.
perform bdc_field using 'BDC_CURSOR'
'KNA1-LZONE'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNA1-STCD1'
record-STCD1_028.
perform bdc_field using 'KNA1-STCD2'
record-STCD2_029.
perform bdc_field using 'KNA1-BBBNR'
record-BBBNR_030.
perform bdc_field using 'KNA1-BBSNR'
record-BBSNR_031.
perform bdc_field using 'KNA1-BUBKZ'
record-BUBKZ_032.
perform bdc_field using 'KNA1-BRSCH'
record-BRSCH_033.
perform bdc_field using 'KNA1-LZONE'
record-LZONE_034.
perform bdc_dynpro using 'SAPMF02D' '0125'.
perform bdc_field using 'BDC_CURSOR'
'KNA1-JMJAH'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNA1-KUKLA'
record-KUKLA_035.
perform bdc_field using 'KNA1-BRSCH'
record-BRSCH_036.
perform bdc_field using 'KNA1-UMSA1'
record-UMSA1_037.
perform bdc_field using 'KNA1-UWAER'
record-UWAER_038.
perform bdc_field using 'KNA1-UMJAH'
record-UMJAH_039.
perform bdc_field using 'KNA1-JMZAH'
record-JMZAH_040.
perform bdc_field using 'KNA1-JMJAH'
record-JMJAH_041.
perform bdc_dynpro using 'SAPMF02D' '0130'.
perform bdc_field using 'BDC_CURSOR'
'KNBK-BANKN(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'KNBK-BANKS(01)'
record-BANKS_01_042.
perform bdc_field using 'KNBK-BANKL(01)'
record-BANKL_01_043.
perform bdc_field using 'KNBK-BANKN(01)'
record-BANKN_01_044.
perform bdc_dynpro using 'SAPMF02D' '0130'.
perform bdc_field using 'BDC_CURSOR'
'KNBK-BANKS(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_dynpro using 'SAPMF02D' '0340'.
perform bdc_field using 'BDC_CURSOR'
'KNVA-KNFAK(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'KNVA-ABLAD(01)'
record-ABLAD_01_045.
perform bdc_field using 'KNVA-KNFAK(01)'
record-KNFAK_01_046.
perform bdc_dynpro using 'SAPMF02D' '0340'.
perform bdc_field using 'BDC_CURSOR'
'RF02D-KUNNR'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_dynpro using 'SAPMF02D' '0370'.
perform bdc_field using 'BDC_CURSOR'
'KNA1-CIVVE'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'KNA1-CIVVE'
record-CIVVE_047.
perform bdc_dynpro using 'SAPMF02D' '0360'.
perform bdc_field using 'BDC_CURSOR'
'KNVK-ABTNR(02)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'KNVK-ANRED(01)'
record-ANRED_01_048.
perform bdc_field using 'KNVK-ANRED(02)'
record-ANRED_02_049.
perform bdc_field using 'KNVK-NAMEV(01)'
record-NAMEV_01_050.
perform bdc_field using 'KNVK-NAMEV(02)'
record-NAMEV_02_051.
perform bdc_field using 'KNVK-NAME1(01)'
record-NAME1_01_052.
perform bdc_field using 'KNVK-NAME1(02)'
record-NAME1_02_053.
perform bdc_field using 'KNVK-TELF1(01)'
record-TELF1_01_054.
perform bdc_field using 'KNVK-TELF1(02)'
record-TELF1_02_055.
perform bdc_field using 'KNVK-ABTNR(01)'
record-ABTNR_01_056.
perform bdc_field using 'KNVK-ABTNR(02)'
record-ABTNR_02_057.
perform bdc_dynpro using 'SAPMF02D' '0360'.
perform bdc_field using 'BDC_CURSOR'
'KNVK-NAMEV(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_dynpro using 'SAPMF02D' '0210'.
perform bdc_field using 'BDC_CURSOR'
'KNB1-AKONT'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNB1-AKONT'
record-AKONT_058.
perform bdc_dynpro using 'SAPMF02D' '0215'.
perform bdc_field using 'BDC_CURSOR'
'KNB1-ZTERM'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNB1-ZTERM'
record-ZTERM_059.
perform bdc_dynpro using 'SAPMF02D' '0220'.
perform bdc_field using 'BDC_CURSOR'
'KNB5-MAHNA'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNB5-MAHNA'
record-MAHNA_060.
perform bdc_dynpro using 'SAPMF02D' '0230'.
perform bdc_field using 'BDC_CURSOR'
'KNB1-VRSNR'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_dynpro using 'SAPMF02D' '0310'.
perform bdc_field using 'BDC_CURSOR'
'KNVV-WAERS'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNVV-BZIRK'
record-BZIRK_061.
perform bdc_field using 'KNVV-AWAHR'
record-AWAHR_062.
perform bdc_field using 'KNVV-WAERS'
record-WAERS_063.
perform bdc_field using 'KNVV-KALKS'
record-KALKS_064.
perform bdc_dynpro using 'SAPMF02D' '0315'.
perform bdc_field using 'BDC_CURSOR'
'KNVV-LPRIO'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNVV-LPRIO'
record-LPRIO_065.
perform bdc_field using 'KNVV-KZAZU'
record-KZAZU_066.
perform bdc_field using 'KNVV-ANTLF'
record-ANTLF_067.
perform bdc_dynpro using 'SAPMF02D' '0320'.
perform bdc_field using 'BDC_CURSOR'
'KNVV-PERFK'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'KNVV-PERFK'
record-PERFK_068.
perform bdc_dynpro using 'SAPMF02D' '1350'.
perform bdc_field using 'BDC_CURSOR'
'RF02D-KUNNR'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_dynpro using 'SAPMF02D' '0324'.
perform bdc_field using 'BDC_CURSOR'
'KNVP-PARVW(01)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_transaction using 'XD01'.
enddo.
perform close_group.
perform close_dataset using dataset.
Reward if found helpful....
Cheers,
Chandra Sekhar. -
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
-
Purchase Info Records ( ME11)
Hi all,
I am trying post Data for Purchase Info Records with Conditions data.
I am using a standard Batch Input Method ( LSMW).
Object 0060
Method 0000
Program Name RM06IBI0
Program Type B Batch Input
I am able to post data only for the condition type PB00. for other condition types FRC1 & FRA1 not able to post the data ( also session is not giving any error).
Therefore I am trying out witH BAPI option ( BAPI_PRICES_CONDITIONS),
when i try to test the BAPI i am getting an error "Record KNUMH = 0000668598,
VARNUMH = 000000000000000000000000000000: det. data missing ( Structue BAPICONDIT) .
i am passing below mentioned values to the structue BAPICONDIT
OPERATION 009
SD_DOC
ITM_NUMBER 000000
COND_NO 0000668598
COND_COUNT 02
APPLICATIO M
COND_TYPE FRC1
SCALETYPE F
SCALE_QTY 0.000
SCALE_VAL 1.000000000
CURRENCKEY USD
CURREN_ISO USD
CALCTYPCON C
COND_VALUE 2.000000000
CONDCURR USD
COND_ISO USD
COND_P_UNT 1
COND_UNIT KG
CONUNITISO KG
NUMCONVERT 1
DENOMINATO 1
BASE_UOM KG
BASEQTYISO KG
CONDITIDX 01
Please Suggest what else needs to be passed to get the BAPI working.
Regards,
Sriramfirst cretae the info records only.
cretae one more program with strctures like below
and pass the info record conditions.
if you use one program its cretae the only PB00, here the loop is one time.
you have to pass more than one its read the multiple records
YPUR_INFO_CONDITIONS Convert Conditions for Info Records
LIFNR C(010) Vendor
MATNR C(018) Material
EKORG C(004) Purch. Organization
WERKS C(004) Plant
YPUR_INFO_CONDITION_ITEM Convert Conditions Item records
MATNR C(018) Material
LIFNR C(010) Vendor
EKORG C(004) Purch. Organization
WERKS C(004) Plant
INFNR C(010) Purchasing Info Rec.
ESOKZ C(001) Info record category
KDATB C(008) Validity Per. Start
KDATE C(008) Validity Period End
KSCHL C(004) Condition Type
KBETR C(011) Condition rate
KONWA C(005) Condition currency
KPEIN C(005) Pricing unit
KMEIN C(003) Unit of measure -
Pricing schema for purchase info records
hi guys!
does anyone knows either SAP standard got function to define pricing schema for PIR? if yes, can you please tell me how to set it up step by step?
Thanks a lot,
crystal.Hi,
there is no separate pricing schema for reading info records.
When creating PO, the system first searches for a purchasing
info record with the combination of vendor/material at purchasing
organization/plant level. If there is no such info record, the system
then search at purchasing organization level. If there is no such
info record here either, you must enter it manually.
If the purchasing info record exist, then valid conditions have
priority during price determination. If an info record does not
contain any conditions or invalid conditions, the system read from
last purchasing document in the info record and then suggest the price
from here. The price determined in this way are default values that
can be changed by the buyer if necessary.
You can save useful quotation data for a material in purchasing
info record. The info record can be created automatically by
setting the info update indicator during quotation maintenance
in the item detail.
Please first check is there any valid info record exist for this
material/vendor. You can always create/change/view it manually
via Ta ME11/ME12/Me13.
Please read also the notes 392988, 456691.
Regards,
Edit -
None approval process for Purchasing Info Record
Hi,
Are there some approval process in SAP for Purchasing Info Record?
Now, we use ME11 to creat Purchasing Info Record. And use ME12 to modify Purchasing Info Record. I feel it is very dangerous. Becase if someone make a mistake. Nobody know.
If the price is lower than actual price, vendor must ask us modify it. If the price is higher than actual price, I am not very sure what will happen.
So, we are seeking for an approval process in SAP system.
Dan Yang>
DanYang!@# wrote:
> Hi,
>
> Are there some approval process in SAP for Purchasing Info Record?
> Now, we use ME11 to creat Purchasing Info Record.
And use ME12 to modify Purchasing Info Record. I feel it is very dangerous.
Becase if someone make a mistake. Nobody know.
>
> If the price is lower than actual price, vendor must ask us modify it.
If the price is higher than actual price, I am not very sure what will happen.
>
> So, we are seeking for an approval process in SAP system.
>
> Dan Yang
There is no approval process in standard,Since it serves as master.
Better provide authorization for ME11 & ME12 to restrict it.
Raise quotation to maintain vendor prices. -
Sales order cost estimate to be updated in Info Record (ME11)
Hi,
We have two plants: (a) Sales plant and (b) Manufacturing Plant.
At sales plant, sales order (external) is created and for same external sales order we create another sales order (internal) at the manufacturing plant.
At the manufacturing plant we have the option of doing sales order cost estimate (VA02/ CK51N).
We want to update info record (ME11) at sales plant with sales order cost estiamte value at the manufacturing plant. How this is possible? please suggest.
Regards,
BijayHi
Ask your SD guy which routine is used during the pricing.. You need to write ABAP code in the routine in order to fetch the values from the Sales Order cost estimate
usually, the sales order cost estimate is stored in EK02 condition type... You can read the value from EK02 cond type in Mfg plant and update it in Sales plant
br, Ajay M -
BAPI/FM for Device Info record
Hi All,
I want to create Device Info records in a mass process. Is there any particular FM/BAPI which i can use.
Also i want to do a mass Billing related installation . Is there any FM/BAPI which i can use for this.
Regards
HaricharanHi Hari,
For Device Info Records - the FM is ISU_S_SMALL_DEVICE_CREATE
For Billing Related Installation - the FM is ISU_S_WORKLIST_INSTALL
You could use ISMW transaction EMIGALL for mass operations
In that case the Migration objects are as follows
Device Info Record - DEVINFOREC
Billing Related Installation - INST_MGMT -
Document type for Purchasing Info Records
I want to know where do we define the document type( IL, IN ) for Purchasing Info Records in Customizing(SPRO).
Are these standards or can we define new document types?Hi
There are 4 categories of info records.
Standard
Subcontract
Consignment
Pipeline
There are two types of Info records maintenance:
1) Cross-plant (where you can maintain your info record at the purchasing organization level); or
2) Plant specific (where the specific plant must be maintained).
Besides, there are two document types of info records being <b>hardcoded</b> in SAP -
1) Purchasing Info Record for stock materials (Document Type IL); and
2) Purchasing Info Record for Material Group (Document Type IN).
regards
Srinivas -
Number Ranges for Purchasing Info Record
Dear Guru's
Number range interval for Purchase info record can be created and assign to group and there are two group for Stock and Non Stock materials.
Now my query is how the system pick the number range ??? Since we don't have any assignment like PR,PO
My requirement is we have 3 company code - I need to have different number ranges for purchase Info record for each company . Guide me to achieve ...
Thanks in advance
Regards
AnandSAP has provided only Two standard document Types for Pur. Info Records.
IL for Stock Material ( with matl No.)
IN For material Group (w/o MMR).
By default, if you enter Matl No. in the initial screen, system automatically picks the doc. type IL and the no. range assigned to it.
If you're not entered matl. no. in the initial screen, and proceed the Transaction further, system picks the doc. type IN and prompts you to enter Matl Group.
In the second case, the system picks up the no. range as per assignment.
Here in your case, you want create a new no. range and assign to your IL/ IN.
For this, you go to the transaction Define No. Ranges in Inforecord, from menu bar, choose Group-> maintain. Here you maintain your new no. range with a name. Now your new group is created with your required no. range.
Then select your new group ( Check box), select, IL, and click assign button and save.. Your IL is assigned to your new group and system picks the new No. Range when you are creating a Inforecord with Mat No. Similarly, you can change No. range for IN also.
or one more option you have.
In the first screen of No. Ranges Transaction, select change intervals tab button, you'll be goto intervals screen. There, from Menu bar, choose Interval-> change current No. Then you reset your current no. to Zero, save it. The again choose Change Interval, then in that screen, change the Interval with your new no. range.
Here in the second case, u need not maintain new groups. Just changing the Interval for the existing group.
You can adopt any one of these options. -
Error in doing LSMW for uploading in Sale order
Dear Sir,
While doing test run for LSMW for uploading 15 Sale order , first order saved with no error and from second order the following error is displayed.
Exchange rate of 1 in INR 2 for date 25.05.2009 3 could not be determined.
Kindly do the needfull.Sir,
If we manually enter, order getting saved for all the sale order.
Why it is not possible while doing LSMW.
Please clarify.
Regards
Sethuraman -
Need to Create the STATUS Profile for Q-Info record
Hi Guys,
Basically in the Q-Info record we have status profiles like VN, SP, MP OM and MP NOM etc... Under this status profiles there are few staus profiles assigned to it, in the same way
I need to create the status profile for Q-Info record under the status profile MP NOM (Non Original Mfgr MP), so that when I am creating the Q-Info record I can select the status profile which is under the MP NOM.
Guys anyone can guide me to create the status profile in BS02.
Regards,
SMBS02--->Select the status say " QM_P_001" ->Copy As F6 - >Enter new name>enter.
Now chage the relevent data as per your requirement. -
Revision: 10891
Author: [email protected]
Date: 2009-10-06 09:46:47 -0700 (Tue, 06 Oct 2009)
Log Message:
Fix for ASDoc throws error when using getter methods for pseudo-inheritance of static constants
QE notes: None.
Doc notes: None
Bugs: SDK-22676
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-22676
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocUtil.javaHave you tried using com.adobe.air.crypto.EncryptionKeyGenerator instead?
-
Creating Conditions for Purchase Info Records using IDoc COND_A01
Hi All,
we are using IDOC COND_A01 to update and add conditions in ME12 transactions.
But when we send a condition IDoc which contains 2 condition types (Segment KONP), the standard function call creates only one database entry in the table KONP. The entry in KONP is for standard condition types PB00, but not for company specific types (Say: ZABC) .But when we create them manually in ME12 maintaining an purchase info record we get both the entries in the KONP database table.
Has anyone come accross such a problem? Is there any special field in the IDoc COND_A01 which controls the creation of the condition types?
Thanks for any answer!U should use basic type INFREC01 instead of NFRECMASS01.
Within the FM there is a check for basic type like:
check idoc type
if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
raise wrong_function_called.
endif.
Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM -
BAPI for Purchase Info record creation - ME11 transaction
Hi,
Is there any bapi or function modules which will create the Purchase info record in Me11 transaction and also bapi for change Purchase info record in Me12 transaction?
Points will be awarded.
Regards,
vinoth.Hi,
ME_MAINTAIN_INFORECORD
ME_UPDATE_INFORECORD
ME_GET_INFORECORD_CONDITIONS
ME_PRICING_INFORECORD.
ME_DIRECT_INPUT_INFORECORD
ME_POST_INFORECORD.
Maybe you are looking for
-
Which Microphone for New Mid 2011 Macbook Air 13"
Please recommend a few USB condensor microphones for voice/vocal recordings that is sure to work with the New Mid 2011 Macbook Air. My 3.5mm to USB adapters that work on my 2009 Macbook Pro with Leopard OS, no longer works with Lion OS Ill be using t
-
What cable should I use to connect my g4 to a 19'flat screen hd tv?
Whats it called? Is it widely available? Want to watch DVD and maybe use it as a second monitor Thanks! Marc
-
Does importing my photos using the connection kit import in full resolution.
I have been using the connection kit to import my photos. I was wondering if it imports them thin full resolution?
-
Can I access Windows machines with my iPad through my home network?
-
Creating Essbase measure hierarchy in OBIEE
Hi All, I have imported Essbase cube(11.1.2) to OBIEE 11.1.1.7 . In RPD i have clicked on "convert measure dimension to flat measures" in physical layer. Now measures are showing up as Meas1