IT 0001

Hi,
We have a unique situation wherein we want a field in IT 0001.
In IT 0001 for the Program MP000100 the Standard Screen is 2000 and it has a field SBMOD (Administrator Group). We want that field to be visible for USA with Screen 2010. We are not able to copy Screen 2000 for USA as Screen 2000 doesnu2019t have the field EXMPT (Indicator: Exempt/non-exempt) which we want in the US Specific Screen. Is it Possible to incorporate the field SBMOD (Administrator Group) in Screen 2010 ( For US)?
Please Advice.
Regards,
Ghanapriya

Hi,
yes you can do it with the help of abaper(they used the cancept field exit or change pointers)
Rupa

Similar Messages

Problem in creation of any purchasing doc against plant 0001

Hi MM Experts,
I am facing problem in creation of any purchasing doc (i.e: PR or PO) against plant 0001.This is available in the system and assigned to company code. I can create Material master with this plant 0001 and copy to create new plant. But Can't create any pur doc? also in plant list in pur doc showing the rest of the plant except plant 0001.
I m working on ECC 6.0.
Regards,

Dear Sairam/Steve,
I got solution for my problem. The problem is that address number not maintained for 0001 plant.This solution available from the following note. please go thro...
Note 433997 introduced a new logic for the F4 help for plants.
solution proposed in note 433997 :
To maintain the address number of a plant subsequently, startTransaction OX10 for the affected plant ('Change plants') view. Click the 'Address' pushbutton (envelope) or (shiftF5). In the subsequent screen ('Change address'), press Enter or click the 'Copy' pushbutton and save using the 'Save' pushbutton (disk) or (CtrlS).
Then the plant should have an address number and should also be displayed in the search help.
Thank you all
Regards,

Cost center (KOSTL) is not updating in HR master table for infotype 0001

Hi ABAP gurus,
We have one interface where we are posting the HR master data using the IDOC (IDOC_INPUT_HRMD) into SAP.
While updating cost center, We have one issue regarding infotype 0001.
It is working fine for all the fields except: KOSTL, ORGEH, STELL. Surprisingly the created IDOC contains the value in these fields but it is not getting updated in master table PA0001. I have tryied inserting the value manually and it is working fine and tried with BDC Programming and no issues. Only we have this issue while we want to use the IDOC. This is mandatory in our interface.
While debugging the IDOC function module I found that one condition is there for these three fields.
CHECK NOT inte IS INITIAL. where inte value is being fetched from table t77s0 based on
GRPID = PLOGI
SEMID = ORGA
In this condition I see no value for this combination and hence it is not getting further. I am not sure how this condition does exist for only these three fields and not for others.
Can any please provide the reasona and solution for this.
Appreciate the help in advance.
Thanks,
Jitender

Dear Mohan,
Try assigning your cost center to position it will default both your org unit and cost center.
Cheers!

MB5B Stock on 01.01.0001

We went live in 2008. For certain materials system shows stock on date 01.01.0001. There are no material documents for these stocks.
Any clues how this would have happened ?

Yes Bayu...thats the exact situtation I am talking about.
These are the details for one material from MB5B:
Plnt Material From Date To Date Opening Stock Total Receipt Qties Total Issue Quantities Closing Stock BUn
CL01 90638582 01.01.0001 31.12.0001 2 0 0 2 SU

Hiding a field in PA30 screen(for inoftype 0001)

Hi All,
I have an requirement that i have to hide a Cost center field in PA30 - for infotype 0001 .
I have maintained v_t588m in SM31 for screen 2000 i have selected the costcenter radiobutton to hide and saved but the changes are not effecting to the PA30 screen
and one more thing again am going and checking to this view the changes are not saved in the view.
Is i have to create new feature for this one ? if created,is have to maintain anything?
Please help on this.
Thanks & Regards,
Anil Kumar.

P0001 Organizational Assignment Infotype (0001): Screen Control Status: Active
5 TCLAS Transaction class for data storage
5 A Master data and time data
5 MOLGA Country Grouping
4 01 Germany
4 07 Canada
4 09 Denmark (DAENEMARK)
 4 10 USA
4 16 South Africa
 4 22 Japan (JAPAN)
 4 23 Sweden (SCHWEDEN)
 4 29 Argentina (ARGENTINA)
 4 34 Indonesia (INDONESIA)
 4 37 Brazil
5 40 India
5 DYNNR Number of the following screen
5 2000
5 3000
5 PERSK (1) Employee Subgroup
5 O
OE
5 otherwise
4 48 Philippines (PHILIPPINES)
 4 otherwise
4 B Applicant data
The Exp Shows for Country India(40) For Dynnr 3000 for Employee Subgroup 0 my Variable is OE.
This is the way U sud search for Variable.
~BiSu
Message was edited by:
 Biswajit Das
Message was edited by:
 Biswajit Das

Component BI_CONT: SP level 0001 is incorrect, expected 6

Hello!
I faced with problem after installed the Solution Manager 7.01 (with SP26)
In step INSTALLATION CHECK on the Diagnostics Prerequisites I get status "Activity Error" with explanation
Component BI_CONT: SP level 0001 is incorrect, expected 6
May be somebody know what I need do?
Or I can do some steps to resolved this problem?
Best regards
Dmitry Zakharenkov

Hi
Please verify the solution manager met all the prerequest specified in the note for ur SP level
[Note 1274287 - End-to-End Diagnostics 7.0 EHP1 SP18 to SP26|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1274287]
if no, please make them equal to the note
and if yes, you can check the fix in the note avoid the activity error
[ Note 1297598 - Fix in prerequisite|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1297598]
Jansi

Error while assigning position in 0001

Hello All,
I'm trying to assign postion in 0001 IT , however I'm getting the error 'Time Constraint allows you to assign only one position'.
Can any one help me on this?
Thanks a lot

HI,
In table V_T777ZVK change the time constraint for Objects S & P for the assignment.
Regards,
Kapil

Urgent: Error-Record 39,779, segment 0001 is not in the cross-record table

Hi Gurus,
This is an urgent production issue: I got the following error-
I am updating data records from a DSO to Infocube in delta mode,
1.Record 39,779, segment 0001 is not in the cross-record table
2.Error in substep: End Routine
I dont know problem is in the End Routine or somewhere else,
The End routine is this:
PROGRAM trans_routine.
 CLASS routine DEFINITION
CLASS lcl_transform DEFINITION.
PUBLIC SECTION.
Attributs
 DATA:
 p_check_master_data_exist
 TYPE RSODSOCHECKONLY READ-ONLY,
*- Instance for getting request runtime attributs;
 Available information: Refer to methods of
 interface 'if_rsbk_request_admintab_view'
 p_r_request
 TYPE REF TO if_rsbk_request_admintab_view READ-ONLY.
PRIVATE SECTION.
 TYPE-POOLS: rsd, rstr.
Rule specific types
 TYPES:
 BEGIN OF tys_TG_1,
 InfoObject: ZVEHICLE Unique Vehicle ID.
 /BIC/ZVEHICLE TYPE /BIC/OIZVEHICLE,
 InfoObject: ZLOCID Mine Site.
 /BIC/ZLOCID TYPE /BIC/OIZLOCID,
 InfoObject: ZLOCSL Location Storage Location.
 /BIC/ZLOCSL TYPE /BIC/OIZLOCSL,
 InfoObject: 0VENDOR Vendor.
 VENDOR TYPE /BI0/OIVENDOR,
 InfoObject: ZNOMTK Nomination Number.
 /BIC/ZNOMTK TYPE /BIC/OIZNOMTK,
 InfoObject: ZNOMIT Nomination Item.
 /BIC/ZNOMIT TYPE /BIC/OIZNOMIT,
 InfoObject: ZNOMNR Nomination number.
 /BIC/ZNOMNR TYPE /BIC/OIZNOMNR,
 InfoObject: ZVSTTIME Vehicle Starting Time Stamp.
 /BIC/ZVSTTIME TYPE /BIC/OIZVSTTIME,
 InfoObject: ZVEDTIME Vehicle Ending Time Stamp.
 /BIC/ZVEDTIME TYPE /BIC/OIZVEDTIME,
 InfoObject: ZNETWT Net Weight.
 /BIC/ZNETWT TYPE /BIC/OIZNETWT,
 InfoObject: TU_GRS_WG Gross Wgt.
 /BIC/TU_GRS_WG TYPE /BIC/OITU_GRS_WG,
 InfoObject: ZTU_TRE_W Tare Wgt.
 /BIC/ZTU_TRE_W TYPE /BIC/OIZTU_TRE_W,
 InfoObject: ZCUSTWT Customer Weight.
 /BIC/ZCUSTWT TYPE /BIC/OIZCUSTWT,
 InfoObject: ZCAR_NO Car Number.
 /BIC/ZCAR_NO TYPE /BIC/OIZCAR_NO,
 InfoObject: ZINBND_ID Train Consist Inbound ID.
 /BIC/ZINBND_ID TYPE /BIC/OIZINBND_ID,
 InfoObject: ZOTBND_ID Train Consist Return Load.
 /BIC/ZOTBND_ID TYPE /BIC/OIZOTBND_ID,
 InfoObject: 0SOLD_TO Sold-to Party.
 SOLD_TO TYPE /BI0/OISOLD_TO,
 InfoObject: 0CUSTOMER Customer Number.
 CUSTOMER TYPE /BI0/OICUSTOMER,
 InfoObject: 0SHIP_TO Ship-To Party.
 SHIP_TO TYPE /BI0/OISHIP_TO,
 InfoObject: ZVEHI_NO Vehicle Number.
 /BIC/ZVEHI_NO TYPE /BIC/OIZVEHI_NO,
 InfoObject: ZCARSTDAT Car Start Date.
 /BIC/ZCARSTDAT TYPE /BIC/OIZCARSTDAT,
 InfoObject: ZCAREDDAT Car End Date.
 /BIC/ZCAREDDAT TYPE /BIC/OIZCAREDDAT,
 InfoObject: ZCARSTTIM Car Start Time.
 /BIC/ZCARSTTIM TYPE /BIC/OIZCARSTTIM,
 InfoObject: ZCAREDTIM Car End Time.
 /BIC/ZCAREDTIM TYPE /BIC/OIZCAREDTIM,
 InfoObject: 0COMPANY Company.
 COMPANY TYPE /BI0/OICOMPANY,
 InfoObject: ZCONTRACT Contract.
 /BIC/ZCONTRACT TYPE /BIC/OIZCONTRACT,
 InfoObject: 0PLANT Plant.
 PLANT TYPE /BI0/OIPLANT,
 InfoObject: ZLOADTIME Total Vehicle Loading time.
 /BIC/ZLOADTIME TYPE /BIC/OIZLOADTIME,
 InfoObject: ZSHIPDATE Shipping Date.
 /BIC/ZSHIPDATE TYPE /BIC/OIZSHIPDATE,
 InfoObject: ZSHIPTIME Shipping Time.
 /BIC/ZSHIPTIME TYPE /BIC/OIZSHIPTIME,
 InfoObject: ZMNEDDT Manifest End Date.
 /BIC/ZMNEDDT TYPE /BIC/OIZMNEDDT,
 InfoObject: ZMNEDTM Manifest End Time.
 /BIC/ZMNEDTM TYPE /BIC/OIZMNEDTM,
 InfoObject: ZLDEDDT Loaded End Date.
 /BIC/ZLDEDDT TYPE /BIC/OIZLDEDDT,
 InfoObject: ZLDEDTM Loaded End Time.
 /BIC/ZLDEDTM TYPE /BIC/OIZLDEDTM,
 InfoObject: ZMANVAR Manifest Variance.
 /BIC/ZMANVAR TYPE /BIC/OIZMANVAR,
 InfoObject: ZTU_TYPE Trpr Unit Type.
 /BIC/ZTU_TYPE TYPE /BIC/OIZTU_TYPE,
 InfoObject: ZACTULQTY Actual posted quantity.
 /BIC/ZACTULQTY TYPE /BIC/OIZACTULQTY,
 InfoObject: ZVEDDT Vehicle End Date.
 /BIC/ZVEDDT TYPE /BIC/OIZVEDDT,
 InfoObject: ZVEDTM Vehicle End Time.
 /BIC/ZVEDTM TYPE /BIC/OIZVEDTM,
 InfoObject: ZVSTDT Vehicle Start Date.
 /BIC/ZVSTDT TYPE /BIC/OIZVSTDT,
 InfoObject: ZVSTTM Vehicle Start Time.
 /BIC/ZVSTTM TYPE /BIC/OIZVSTTM,
 InfoObject: ZTRPT_TYP Vehicle type.
 /BIC/ZTRPT_TYP TYPE /BIC/OIZTRPT_TYP,
 InfoObject: 0CALMONTH Calendar Year/Month.
 CALMONTH TYPE /BI0/OICALMONTH,
 InfoObject: 0CALYEAR Calendar Year.
 CALYEAR TYPE /BI0/OICALYEAR,
 InfoObject: ZLOEDDT Quality Sent End Date.
 /BIC/ZLOEDDT TYPE /BIC/OIZLOEDDT,
 InfoObject: ZLOEDTM Quality sent End Time.
 /BIC/ZLOEDTM TYPE /BIC/OIZLOEDTM,
 InfoObject: ZATMDDT At Mine End Date.
 /BIC/ZATMDDT TYPE /BIC/OIZATMDDT,
 InfoObject: ZATMDTM At Mine End Time.
 /BIC/ZATMDTM TYPE /BIC/OIZATMDTM,
 InfoObject: ZDELAY Delay Duration.
 /BIC/ZDELAY TYPE /BIC/OIZDELAY,
 InfoObject: ZSITYP Schedule type.
 /BIC/ZSITYP TYPE /BIC/OIZSITYP,
 InfoObject: ZDOCIND Reference document indicator.
 /BIC/ZDOCIND TYPE /BIC/OIZDOCIND,
 InfoObject: 0BASE_UOM Base Unit of Measure.
 BASE_UOM TYPE /BI0/OIBASE_UOM,
 InfoObject: 0UNIT Unit of Measure.
 UNIT TYPE /BI0/OIUNIT,
 InfoObject: ZACT_UOM Actual UOM.
 /BIC/ZACT_UOM TYPE /BIC/OIZACT_UOM,
 Field: RECORD.
 RECORD TYPE RSARECORD,
 END OF tys_TG_1.
 TYPES:
 tyt_TG_1 TYPE STANDARD TABLE OF tys_TG_1
 WITH NON-UNIQUE DEFAULT KEY.
$$ begin of global - insert your declaration only below this line -
... "insert your code here
$$ end of global - insert your declaration only before this line -
 METHODS
 end_routine
 IMPORTING
 request type rsrequest
 datapackid type rsdatapid
 EXPORTING
 monitor type rstr_ty_t_monitors
 CHANGING
 RESULT_PACKAGE type tyt_TG_1
 RAISING
 cx_rsrout_abort.
 METHODS
 inverse_end_routine
 IMPORTING
 i_th_fields_outbound TYPE rstran_t_field_inv
 i_r_selset_outbound TYPE REF TO cl_rsmds_set
 i_is_main_selection TYPE rs_bool
 i_r_selset_outbound_complete TYPE REF TO cl_rsmds_set
 i_r_universe_inbound TYPE REF TO cl_rsmds_universe
 CHANGING
 c_th_fields_inbound TYPE rstran_t_field_inv
 c_r_selset_inbound TYPE REF TO cl_rsmds_set
 c_exact TYPE rs_bool.
ENDCLASS. "routine DEFINITION
$$ begin of 2nd part global - insert your code only below this line *
... "insert your code here
$$ end of 2nd part global - insert your code only before this line *
 CLASS routine IMPLEMENTATION
CLASS lcl_transform IMPLEMENTATION.
 Method end_routine
 Calculation of result package via end routine
 Note: Update of target fields depends on rule assignment in
 transformation editor. Only fields that have a rule assigned,
 are updated to the data target.
<-> result package
METHOD end_routine.
*=== Segments ===
 FIELD-SYMBOLS:
 <RESULT_FIELDS> TYPE tys_TG_1.
 DATA:
 MONITOR_REC TYPE rstmonitor.
*$*$ begin of routine - insert your code only below this line *-*
Fill the following fields by reading Nomination and Vehicls DSO
SOLD_TO, Customer
data: L_TIMESTAMP1 TYPE timestamp,
 L_TIMESTAMP2 TYPE timestamp,
 L_TIMESTAMP3 type CCUPEAKA-TIMESTAMP,
 L_TIMESTAMP4 type CCUPEAKA-TIMESTAMP,
 L_TIMESTAMP5 type CCUPEAKA-TIMESTAMP,
 L_TIMESTAMP6 type CCUPEAKA-TIMESTAMP,
 L_TIMESTAMP7 TYPE timestamp,
 L_TIMESTAMP8 TYPE timestamp,
 L_TIMESTAMP9 type timestamp,
 L_TIMESTAMP10 type TIMESTAMP,
 L_CHAR1(14),
 L_CHAR2(14),
 l_duration type I,
 L_TS TYPE TZONREF-TZONE,
 l_flag,
 l_nomit TYPE /BIC/OIZNOMIT,
 l_error_flag.
l_TS = 'CST'.
Data: EXTRA_PACKAGE type tyt_TG_1.
data: extra_fields type tys_TG_1.
LOOP at RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
clear l_error_flag.
Get sold_to and customer from nomination table.
 Select single SOLD_TO /BIC/ZLOCSL /BIC/ZCONTRACT COMPANY
 /BIC/ZMNEDDT /BIC/ZMNEDTM /BIC/ZLDEDDT
 /BIC/ZLDEDTM SHIP_TO /BIC/ZACTULQTY
 /BIC/ZLOEDDT /BIC/ZLOEDTM /BIC/ZDELAY
 /BIC/ZATMDDT /BIC/ZATMDTM
 /BIC/ZSITYP /BIC/ZDOCIND
 into (<RESULT_FIELDS>-SOLD_TO,
 <RESULT_FIELDS>-/BIC/ZLOCSL,
 <RESULT_FIELDS>-/BIC/ZCONTRACT,
 <RESULT_FIELDS>-company,
 <RESULT_FIELDS>-/BIC/ZMNEDDT,
 <RESULT_FIELDS>-/BIC/ZMNEDTM,
 <RESULT_FIELDS>-/BIC/ZLDEDDT,
 <RESULT_FIELDS>-/BIC/ZLDEDTM,
 <RESULT_FIELDS>-SHIP_TO,
 <RESULT_FIELDS>-/BIC/ZACTULQTY,
 <RESULT_FIELDS>-/BIC/ZLOEDDT,
 <RESULT_FIELDS>-/BIC/ZLOEDTM,
 <RESULT_FIELDS>-/BIC/ZDELAY,
 <RESULT_FIELDS>-/BIC/ZATMDDT,
 <RESULT_FIELDS>-/BIC/ZATMDTM,
 <RESULT_FIELDS>-/BIC/ZSITYP,
 <RESULT_FIELDS>-/BIC/ZDOCIND)
 from /BIC/AZTSW_0000
 where /BIC/ZNOMTK = <RESULT_FIELDS>-/BIC/ZNOMTK
 AND /BIC/ZNOMIT = <RESULT_FIELDS>-/BIC/ZNOMIT.
Select Invalid Nominations
if sy-subrc <> 0.
 l_error_flag = 'X'.
endif.
 <RESULT_FIELDS>-customer = <RESULT_FIELDS>-SOLD_TO.
Prepare time stamp for Time Differences
Vehicle Starting Time Stamp
clear : L_TIMESTAMP9,L_TIMESTAMP10.
CONVERT DATE <RESULT_FIELDS>-/BIC/ZCARSTDAT TIME
 <RESULT_FIELDS>-/BIC/ZCARSTTIM
 INTO TIME STAMP L_TIMESTAMP9 TIME ZONE l_TS.
Vehicle Ending Time Stamp
CONVERT DATE <RESULT_FIELDS>-/BIC/ZCAREDDAT TIME
 <RESULT_FIELDS>-/BIC/ZCAREDTIM
 INTO TIME STAMP L_TIMESTAMP10 TIME ZONE l_TS.
Clear : L_TIMESTAMP3, L_TIMESTAMP4,
 <RESULT_FIELDS>-/BIC/ZVEDTIME,
 <RESULT_FIELDS>-/BIC/ZVSTTIME.
<RESULT_FIELDS>-/BIC/ZVEDTIME = L_TIMESTAMP10.
<RESULT_FIELDS>-/BIC/ZVSTTIME = L_TIMESTAMP9.
L_TIMESTAMP3 = L_TIMESTAMP10.
L_TIMESTAMP4 = L_TIMESTAMP9.
Caliculate the load time
IF L_TIMESTAMP3 is initial.
 clear <RESULT_FIELDS>-/BIC/ZLOADTIME.
elseif L_TIMESTAMP4 is initial.
 clear <RESULT_FIELDS>-/BIC/ZLOADTIME.
else.
 CALL FUNCTION 'CCU_TIMESTAMP_DIFFERENCE'
 EXPORTING
 timestamp1 = L_TIMESTAMP3
 timestamp2 = L_TIMESTAMP4
 IMPORTING
 DIFFERENCE = <RESULT_FIELDS>-/BIC/ZLOADTIME
ENDIF.
Caliculate the Manifest Variance
 clear : L_TIMESTAMP5,L_TIMESTAMP6,L_TIMESTAMP7,L_TIMESTAMP8.
 CONVERT DATE <RESULT_FIELDS>-/BIC/ZMNEDDT TIME
 <RESULT_FIELDS>-/BIC/ZMNEDTM
 INTO TIME STAMP L_TIMESTAMP7 TIME ZONE l_TS.
 CONVERT DATE <RESULT_FIELDS>-/BIC/ZLDEDDT TIME
 <RESULT_FIELDS>-/BIC/ZLDEDTM
 INTO TIME STAMP L_TIMESTAMP8 TIME ZONE l_TS.
L_TIMESTAMP5 = L_TIMESTAMP7.
L_TIMESTAMP6 = L_TIMESTAMP8.
Caliculate the Maniefest Variance
IF L_TIMESTAMP5 is initial.
 clear <RESULT_FIELDS>-/BIC/ZMANVAR.
elseif L_TIMESTAMP6 is initial.
 clear <RESULT_FIELDS>-/BIC/ZMANVAR.
else.
 CALL FUNCTION 'CCU_TIMESTAMP_DIFFERENCE'
 EXPORTING
 timestamp1 = L_TIMESTAMP5
 timestamp2 = L_TIMESTAMP6
 IMPORTING
 DIFFERENCE = <RESULT_FIELDS>-/BIC/ZMANVAR
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
ENDIF.
Delete datapackets with blank nominations
Delete datapackets with blank shipdate and Invalid Time Stamps
*IF <RESULT_FIELDS>-/BIC/ZNOMTK IS INITIAL OR
<RESULT_FIELDS>-/BIC/ZSHIPDATE IS INITIAL.
l_error_flag = 'X'.
*ENDIF.
<RESULT_FIELDS>-/BIC/ZVEHI_NO = 1.
<RESULT_FIELDS>-CALMONTH = <RESULT_FIELDS>-/BIC/ZSHIPDATE(6).
<RESULT_FIELDS>-CALYEAR = <RESULT_FIELDS>-/BIC/ZSHIPDATE(4).
if l_error_flag = 'X'.
Looks like Monitor Entries are not working in SP11.
Hence the following is commented temporarily.
CLEAR MONITOR_REC.
MONITOR_REC-MSGID = '0M'.
MONITOR_REC-MSGTY = 'S'.
MONITOR_REC-MSGNO = '501'.
MONITOR_REC-MSGV1 = <RESULT_FIELDS>-/BIC/ZNOMTK.
MONITOR_REC-recno = sy-tabix.
APPEND MONITOR_REC to MONITOR.
RAISE exception type CX_RSROUT_ABORT.
DELETE RESULT_PACKAGE index sy-tabix.
CLEAR L_ERROR_FLAG.
else.
 MODIFY RESULT_PACKAGE FROM <RESULT_FIELDS>.
endif.
clear l_nomit.
l_nomit = <RESULT_FIELDS>-/BIC/ZNOMIT.
extra_fields = <RESULT_FIELDS>.
Actual Qty and Contract details
 Select /BIC/ZLOCSL /BIC/ZNOMIT /BIC/ZCONTRACT /BIC/ZACTULQTY
 /BIC/ZSITYP /BIC/ZDOCIND
 SOLD_TO SHIP_TO COMPANY
 into (extra_fields-/BIC/ZLOCSL,
 extra_fields-/BIC/ZNOMIT,
 extra_fields-/BIC/ZCONTRACT,
 extra_fields-/BIC/ZACTULQTY,
 extra_fields-/BIC/ZSITYP,
 extra_fields-/BIC/ZDOCIND,
 extra_fields-SOLD_TO,
 extra_fields-SHIP_TO,
 extra_fields-company)
 from /BIC/AZTSW_0000
 where /BIC/ZNOMTK = <RESULT_FIELDS>-/BIC/ZNOMTK AND
 /BIC/ZNOMIT <> l_NOMIT.
 INSERT extra_fields into table EXTRA_PACKAGE.
 endselect.
ENDLOOP.
Append lines of extra_package to RESULT_PACKAGE.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
 raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line -
ENDMETHOD. "end_routine
 Method inverse_end_routine
 This subroutine needs to be implemented only for direct access
 (for better performance) and for the Report/Report Interface
 (drill through).
 The inverse routine should transform a projection and
 a selection for the target to a projection and a selection
 for the source, respectively.
 If the implementation remains empty all fields are filled and
 all values are selected.
METHOD inverse_end_routine.
$$ begin of inverse routine - insert your code only below this line-
... "insert your code here
$$ end of inverse routine - insert your code only before this line -
ENDMETHOD. "inverse_end_routine
ENDCLASS. "routine IMPLEMENTATION

Hi,
Most probably you are appending some records in the data package or deleting from the data package through end routine or expert routine or start routine.
I just solved it.....you will have to import the note 1180163.
Then modify the code which you are using....and include the function module as mentioned in the note 1223532.
You need to add the function module just before you append the records.This will work perfectly.
Thanks
Ajeet

Error REP-0001 While starting the Report service

Hi
When trying to start the reports service from 9iAS, i am getting error message as "REP-0001 Unable to open the message file", and in the Window Title it shows "Message 16200 not found, No message file for product rw".
Regards
Ranganath

Hi,
You(The user) need to have access permission to read the mesg files. The DBA installing Reports will be able to run the reports.
Grant read access to rwus.msb and rwus.msg files on $ORACLE_HOME/reports/mesg/
Try to run it, should work.
Thanks,
Oracle Reports Team.

Posting only possible in periods 2002/03 and 2002/02 in company code 0001

All
This is in the ongoing sequence where I am creating everything from the scratch(customers, material, prices etc).So far, I have been able to create and save the salesorder>deliver it>pick the items and then I was going to carry out the PGI and then this happened.
when I use the date i.e(Planned GI) 27-09-2006, I receive the following error
****************snip********************
Goods movement: Error log
Item   Material           Description                                   Delivery qty UoM Batch
000010 9                  T-AS1_MATERIAL__9                                      10 PC
       E M7 053
       Posting only possible in periods 2002/03 and 2002/02 in company code 0001
************End snip*********************
If I use a date as R/3 wants ,say 27.02.2002(Planned GI),I get:-
"Picking date is after goods issue date"...which is obvious.
any day after 27-09-2006, say 28-09-2006(Planned GI), I get :-
"Goods issue date is later than delivery date"...makes sence too
one thing was clear here to me, I can only post in Feb/March 2002, while my delivery date is 27 Sept 2006 . So I am in a classic chicken-egg situation.
where and who is giving this "Posting only possible in periods 2002/03 and 2002/02 in company code 0001" message ? How can I override this thing from the past ?
I thought of playing it smart and change my system date to the year Feb. 2002 , but in the fear that a lot of other things will fall as a result of that, I did refrain from doing so.
Could someone make this PGI succesful for me
Thanks for any lessons.

Thanks Mr. Srinivas
MMPV was indeed the magic wand.
PGI was successful.
this is my overall document flow as of now :-
Standard Order 2                                27.09.06 Completed
. Outbound delivery 80000000                    27.09.06 Completed
.. WMS transfer order 1                         29.09.06 Completed
.. GD goods issue:delvy 4900000020              30.09.06 complete
.. Invoice 90000000                             30.09.06 Missing export data
As I understand, my invoicing is not yet complete , it's got a number and got saved, but how shall I get rid of that red line message "Missing export data"(foriegn trade data incomplete...was the message while saving the billing document).I would be darn happy if I could just get rid of the foreign data part completely(just want to complete the invoice).Would this be checking off a mandatory rqmt. somewhere in the master data?
and would this also be the reason, why I see no accounting document which should have been on status 'open' by now ?
Thanks in advance ,

Error in info type 0001

Hi all
when hired an employee, while saving 0001 info type inpa40
system shows one error
" Define a fiscal year variant first for company code 9369"
anyone solve prob
thanks and regards
Seenu

thanks for reply
after filled this table (V_001_U) i got one error in info type 0001
"Define a chart of accounts first for company code 9369"

Account Determination for entry 1000 KBS 0001 ---- 2030 error in MIGO

Dear All
A PO has been made with acc. assgnment as "Z" i.e capital order with account modifier as ZCA in OME9 transaction.For this account modifier and valuation class of material an entry is there in OBYC GBB trasaction..
But when I am doing GRN thru MIGOerror is coming as "Account Determination for entry 1000 KBS 0001 -
2030" not possible.
Is any more config is missing?
Pls help.
Regards
SK

satish kumar wrote:
Dear All
>
> A PO has been made with acc. assgnment as "Z" i.e capital order with account modifier as ZCA in OME9 transaction.For this account modifier and valuation class of material an entry is there in OBYC GBB trasaction..
>
> But when I am doing GRN thru MIGOerror is coming as "Account Determination for entry 1000 KBS 0001 -
2030" not possible.
>
> Is any more config is missing?
>
> Pls help.
>
> Regards
> SK
HI,
go through with this link.
Error:Account determination for entry 1000 KBS 0001 not possible
in omjj select movement type give 101 movement type and click on account grouping code check wether the KBS was ticked or not.
Thanking you.

HR Data Load with FM HR_MAINTAIN_MASTERDATA for IT 0000, 0001, 0002...

Hello All!
I am trying to load Infotypes 0000, 0001 and 0002. I will have to load some others too, but I am already having trouble to fill this ones that are the main Infotypes.
I´m using the parameter DIALOG_MODE = '1' so I can see the error. and I can see that some fields that I have Filled on the table
"proposed_values" are not going to the screen. In fact, just the filds of structure P0002 are going. But I have to fill some other filds like Q0002-ANREX, Q0002-FATXT and P0625-RACE.
It is possible to fill this others fields? or should I forget this FM and try BDC/ Batch Input?
This is a sample code that I am testing:
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-NACHN'.
t_pprop-FVAL = 'Colgate'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-VORNA'.
t_pprop-FVAL = 'Márcio'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-GBDAT'.
t_pprop-FVAL = '19690609'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-GBDEP'.
t_pprop-FVAL = 'BA'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-GBORT'.
t_pprop-FVAL = 'Feira de Santana'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-GBLND'.
t_pprop-FVAL = 'BR'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'P0002-NATIO'.
t_pprop-FVAL = 'BR'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'Q0002-ANREX'.
t_pprop-FVAL = 'Sr.'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'Q0002-GESC1'.
t_pprop-FVAL = 'X'.
APPEND t_pprop.
t_pprop-INFTY = '0002'.
t_pprop-FNAME = 'Q0002-FATXT'.
t_pprop-FVAL = 'Solt'.
APPEND t_pprop.
t_pprop-INFTY = '0625'.
t_pprop-FNAME = 'P0625-RACE'.
t_pprop-FVAL = '0'.
APPEND t_pprop.
v_pernr = s_0002-pernr.
   CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
     EXPORTING
       PERNR                    = v_pernr
       ACTIO                    = 'INSS'
       TCLAS                    = 'B'
        BEGDA                    = sy-datum
        DIALOG_MODE              = '1'
       NO_EXISTENCE_CHECK       = 'X'
     IMPORTING
       RETURN                   = s_return
       RETURN1                  = s_return1
      TABLES
        proposed_values          = t_pprop.
    CLEAR s_return1.
    CALL FUNCTION 'HR_EMPLOYEE_DEQUEUE'
      EXPORTING
        number        = v_pernr
      IMPORTING
        RETURN        = s_return1.
Thanks in Advance.
Jonas

Hi,
First try to load Infotypes 0000, 0001 and 0002 only, remove other fields from the Proposed Values internal table as that seems to be creating problem.
Once the FM execute without any error, then try to insert values for other tables.
Regards,
Nitin Gaikwad

Additional field in 0001 info type

Hi all,
I want to add a new field in 0001 info type.
i believe this is just enhancement.
Could you pls suggest the ways to enhance the 0001 info type accordingly..?
Thanks & Regards,

1. Using transaction PM01 chose the 'Enhance Infotype tab' and press the create 'All' button.
2. In the next screen enter the new fields you wish to add to the Infotype 0001.
3. After Saving and Activating check the screen(using PA20 / PA30) and table PA0001. You will be able to see your new field.

Additional field in Infotype 0001

I manage to add an additional field in the infotype 0001 in Dev client. I have a bit concern when to apply it in the production client.
Do you have any experience to share on this?

hi
test in development server later test in testing server later send it to production server
nothing to worry
all the best

Cost center is not updating in IT 0001

Dear Mates,
I've uploaded two sets of data using PP02 T-code where one is Historical data & the other is Current data. Here for Current data I'm facing a Issue where Cost center & org unit's data aren't getting updated in IT 0001 & its still showing the Historical data in IT0001. This is even spoiling the show & frustrating, where users are unable to do CATS Reconciliation also. for more clarification kindly find below screenshots.
PO13
We have maintained historical data in system where one cost center is assigned from 01.01.2013 to 31.03.2014 & second cost center is assigned from 01.04.2014 to 31.12.9999 with current period, not only cost center's but also Org unit's are also not updating in the system. I've even tried with RHINTE00,10,20 & 30 program's but still I'm unable to get the desired results.
Historical data from 12.11.2013 to 31.03.2014 in IT0001
Current record 01.04.2014 to 31.12.9999 in IT0001
Kindly let me know how to update IT0001.Is there any std program available to update the data apart from RHINTE**???
Ur's
Mohan

Dear Mohan,
Try assigning your cost center to position it will default both your org unit and cost center.
Cheers!

IT 0001

Similar Messages

Maybe you are looking for