Real time problems

< MODERATOR: Message locked. Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. no interview questions please. >
pls answer to the following questions,if it will be useful then you will be appreciated.
1 suppose in f-02 you didnot fill any thing in profit center field ,then it will gives the error,what you have to do?
2 dummy profit center is mandatory/not?
3 in a/r how can you enter the cash against customer?
4how can we deliver the stock to customer without invoice creation?
5 can you change the payment terms in vendor master record?
regards
jana

Hello Pramod,
There are many common problems during implementation / rollouts and these are mentioned in FAQs on OSS also SAP has suggested way on how to handle this so search with FAQs in OSS in the area of Material Management.
Also, you can go through success story on SAP website which will give you some highlights on Challenges.
There are some books available on implementing SAP sucessfully which explains the tips on how to handle SAP implementation.
here is some information
http://www.sap-img.com/sap-implementation.htm
<a href="http://amazon.com/s/ref=nb_ss_gw/102-7813067-4131348?url=search-alias%3Daps&field-keywords=sap+implementation">Books on Amazon</a>
If you have some particular query, please let us know.
Regards
Arif Mansuri

Similar Messages

Hi , any body can send real time problems they faced

hi every body this is siva from banglore, any body can send the real time problems they faced in sap crm and how they solved if any body kindly send to my id : [email protected]

hi Siva,
All the issues in the forums are the real time issues
YOu can just go through them .
Also why do you need real time issues.
If you have any issues post it here and some one can help you

Compress Infocube Real Time problem - performance

Hello All!
I am having a problem with a cube and not able to compress the requests , repare indices , save data in this cube......please help!!
If I start the jobs they did not finish and if i try to run and save a planning sequence i got an error (OR A-14400 inserted partition key does not map at any partition.....the cube is not partioned.
I also tried to repare in RSRV and it get locked , never end.
This is real time infocube.
Let me know your commnents guys
Thank you
RDP

See if the below threads help you in some way:
ORA-14400: inserted partition key does not map to any partition
"ORA-14400: inserted partition key does not map to any partition"

How to Create an Epic Rap Battle of History in After Effects (Compositing, VFX, Green Screen, Audio), or Fix Audio, Speed, and Real Time Problems

Hello. As a film project, I am creating an "Epic Rap Battle of History", a parody video of a popular series on YouTube. In my film/video, I would like to use compositing so that there will be two of one character in one shot. I have used Premiere Pro CC for the main character sequences, but when I imported this project in After Effects, there was no audio at all from the song, and the canvas displaying the composition was moving very slowly, at about 50% of the video's actual speed. Also, in the top right corner, it says, "Not Real Time", and displays something like 7.39/29.96. I have looked at different web pages, and nothing seems to work.
I would appreciate it if someone could explain how to fix this all up for me, or especially if someone who has had experience creating an Epic Rap Battle could actually list a step-by-step process on how to create one.
If this helps, I am a beginner to Adobe, and work on a iMac tower. Thank you for your feedback.

Start here to learn After Effects: http://adobe.ly/AE_basics

What kind of real time problems and issues arise in Data Modelling

Hellooo experts,
I am not a BW expertise, so just want to gather some knowledge on Problems and issues related to DATA MODELLING, if any body have a document or a link can you please snd it to [email protected] or reply to this post. I promise to reward you for proper answers hope this is the way i say thanks for your help.
kishore

hi kishore,
The first and most important problem is to understand Clients requirement. Clients even some time not aware of how to utilize efficiency of BW, as they are very much use to with traditional SAP R/3 reporting. So most of time we have to suggest options to client.
If we come to technical aspect, than identifying Key Figures and Characterstics is the most important task. And how you map that to available infoobjects. Attributes also plays major roles, like which attributes is better to use as navigational one and which as exclusive attribute.
Their is long list for data modelling issues, its better you refer either Mastering BIW book by Mac'Donalds. And SAP Help Library is also having good material.
regards,
kamaljeet

Send me any real time problems(tickets) in sap fi/co support project

i want clear information

Hi
Check the link below.
http://sap-img.com/human/time-management-queries.htm
This will provide you questions on time management.
Reward Points if it helps.
Regards
Karan

How can i know more trouble shooting issues/Real time problems and thier solutions?

Hi to every one.
i am Technician in a reputed mnc company. I am new to Microsoft servers. I learned MCSE 2008 and have basic trouble shooting knowledge.To improve my knowledge on these servers and how can i know real issues in a company occurs , solution to them. Please
help me to get more knowledge on these servers.
I am waiting for your reply.
Thanks & Regards,
Praveen

If you want to know more about issues related to your own internal servers, I'd simply start by reviewing the event logs and running perfmon in the short term to look for issues. For more long term management and monitoring I'd look to a tool
like System Center Operations Manager:
http://technet.microsoft.com/en-us/library/hh205987.aspx
For general troubleshooting skills growth, I'd stick around these forums and just read issues as they occur and try to assist with resolving some that you feel you can.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

It's urgent - - - Real time Problem

hi experts,
i am working on aging report. its a interactive report.
now wht i want is that document type DR should also get totalled in the base report
but this report is not doing so.
please help me out that how can i include dr in the aging also.
attaching u the code for the base report
*& Report ZAGING1
REPORT zage_ver1 NO STANDARD PAGE HEADING LINE-SIZE 250.
TABLES : bseg, kna1 ,bsad, bsid, vbrk.
SELECT-OPTIONS: s_kunnr FOR kna1-kunnr OBLIGATORY.
PARAMETERS : key_date TYPE bldat OBLIGATORY.
PARAMETERS : ccode TYPE bukrs OBLIGATORY.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 01(30) text-001 FOR FIELD int1.
SELECTION-SCREEN POSITION POS_LOW.
PARAMETERS: int1(3) TYPE n DEFAULT '030'.
PARAMETERS: int2(3) TYPE n DEFAULT '060'.
PARAMETERS: int3(3) TYPE n DEFAULT '090'.
PARAMETERS: int4(3) TYPE n DEFAULT '120'.
PARAMETERS: int5(3) TYPE n DEFAULT '150'.
SELECTION-SCREEN END OF LINE.
DATA : onacc LIKE bsid-wrbtr.
TYPES: BEGIN OF cust,
 kunnr TYPE kna1-kunnr,
 adrnr TYPE kna1-adrnr,
 name1 TYPE kna1-name1,
 wrbtr TYPE bseg-wrbtr,
 bzirk TYPE knvv-bzirk,
 zterm TYPE knvv-zterm,
 ztag1 TYPE t052-ztag1,
 END OF cust.
TYPES: BEGIN OF invt,
 kunnr TYPE kna1-kunnr,
 kunrg TYPE kna1-kunnr,
 wrbtr TYPE bseg-wrbtr,
 invamt TYPE bseg-wrbtr,
 name1 TYPE kna1-name1,
 vbeln TYPE vbrk-vbeln,
 belnr TYPE bseg-belnr,
 END OF invt.
TYPES : BEGIN OF ytab,
 kunnr TYPE bsid-kunnr,
 wrbtr TYPE bsid-wrbtr,
 sinv_amt TYPE bsid-wrbtr,
 paid_amt TYPE bsid-wrbtr,
 adj_amt TYPE bsid-wrbtr,
 cncl_amt TYPE bsid-wrbtr,
 baln_amt TYPE bsid-wrbtr,
 onac_amt TYPE bsid-wrbtr,
 ac_amt TYPE bsid-wrbtr,
 age_amt TYPE bsid-wrbtr,
 wrbtr_rvh TYPE bsid-wrbtr,
 wrbtr_rvs TYPE bsid-wrbtr,
 wrbtr_obh TYPE bsid-wrbtr,
 wrbtr_obs TYPE bsid-wrbtr,
 wrbtr_dg TYPE bsid-wrbtr,
 wrbtr_dr TYPE bsid-wrbtr,
 wrbtr_dzs TYPE bsid-wrbtr,
 wrbtr_dzh TYPE bsid-wrbtr,
 wrbtr_sas TYPE bsid-wrbtr,
 wrbtr_sah TYPE bsid-wrbtr,
 wrbtr_abs TYPE bsid-wrbtr,
 wrbtr_abh TYPE bsid-wrbtr,
 baln1 TYPE bsid-wrbtr,
 baln2 TYPE bsid-wrbtr,
 baln3 TYPE bsid-wrbtr,
 baln4 TYPE bsid-wrbtr,
 baln5 TYPE bsid-wrbtr,
 baln6 TYPE bsid-wrbtr,
 blart TYPE bsid-blart,
 vbeln TYPE bsid-vbeln,
 fkdat TYPE vbrk-fkdat,
 belnr TYPE bsid-belnr,
 rebzg TYPE bsid-rebzg,
 shkzg TYPE bsid-shkzg,
 zuonr TYPE bsid-zuonr,
 od_days(4) TYPE n,
 END OF ytab.
TYPES : BEGIN OF ftab,
 kunnr TYPE bsid-kunnr,
 name1 TYPE kna1-name1,
 WRBTR TYPE BSID-WRBTR,
 sinv_amt TYPE bsid-wrbtr,
 paid_amt TYPE bsid-wrbtr,
 adj_amt TYPE bsid-wrbtr,
 cncl_amt TYPE bsid-wrbtr,
 baln_amt TYPE bsid-wrbtr,
 ac_amt TYPE bsid-wrbtr,
 onac_amt TYPE bsid-wrbtr,
 outs_amt TYPE bsid-wrbtr,
 age_amt TYPE bsid-wrbtr,
 wrbtr_rvh TYPE bsid-wrbtr,
 wrbtr_rvs TYPE bsid-wrbtr,
 wrbtr_obh TYPE bsid-wrbtr,
 wrbtr_obs TYPE bsid-wrbtr,
 wrbtr_dg TYPE bsid-wrbtr,
 wrbtr_dr TYPE bsid-wrbtr,
 wrbtr_dzs TYPE bsid-wrbtr,
 wrbtr_dzh TYPE bsid-wrbtr,
 wrbtr_sas TYPE bsid-wrbtr,
 wrbtr_sah TYPE bsid-wrbtr,
 wrbtr_abs TYPE bsid-wrbtr,
 wrbtr_abh TYPE bsid-wrbtr,
 baln1 TYPE bsid-wrbtr,
 baln2 TYPE bsid-wrbtr,
 baln3 TYPE bsid-wrbtr,
 baln4 TYPE bsid-wrbtr,
 baln5 TYPE bsid-wrbtr,
 baln6 TYPE bsid-wrbtr,
 blart TYPE bsid-blart,
 vbeln TYPE bsid-vbeln,
 belnr TYPE bsid-belnr,
 rebzg TYPE bsid-rebzg,
 shkzg TYPE bsid-shkzg,
 bzirk TYPE knvv-bzirk,
 zterm TYPE knvv-zterm,
 ztag1 TYPE t052-ztag1,
 zuonr TYPE bsid-zuonr,
 od_days(4) TYPE n,
 sno(3) TYPE n,
 END OF ftab.
data : wrbtr_note like bsid-wrbtr.
 DATA : BEGIN OF itab1 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
 xblnr LIKE bsid-xblnr,
 abc LIKE bsid-wrbtr,
 aaa LIKE bsid-wrbtr,
 sgtxt LIKE bsid-sgtxt,
 bcd LIKE bsid-wrbtr,
 bbb LIKE bsid-wrbtr,
 flag TYPE c,
 flag1(3) TYPE c,
 flag2(15) TYPE c,
 bldat like bsid-bldat,
 END OF itab1.
 DATA : BEGIN OF itab2 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
xblnr LIKE bsid-xblnr,
sgtxt LIKE bsid-sgtxt,
abc LIKE bsid-wrbtr,
aaa LIKE bsid-wrbtr,
bcd LIKE bsid-wrbtr,
bbb LIKE bsid-wrbtr,
flag TYPE c,
flag1(3) TYPE c,
flag2(15) TYPE c,
bldat like bsid-bldat,
 END OF itab2.
DATA : BEGIN OF itab3 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
 xblnr LIKE bsid-xblnr,
 abc LIKE bsid-wrbtr,
aaa LIKE bsid-wrbtr,
bcd LIKE bsid-wrbtr,
bbb LIKE bsid-wrbtr,
flag TYPE c,
flag1(3) TYPE c,
flag2(15) TYPE c,
sgtxt LIKE bsid-sgtxt,
bldat like bsid-bldat,
 END OF itab3.
DATA : BEGIN OF itab4 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
xblnr LIKE bsid-xblnr,
aaa LIKE bsid-wrbtr,
abc LIKE bsid-wrbtr,
bbb LIKE bsid-wrbtr,
bcd LIKE bsid-wrbtr,
flag TYPE c,
flag1(3) TYPE c,
flag2(15) TYPE c,
sgtxt LIKE bsid-sgtxt,
bldat like bsid-bldat,
 END OF itab4.
DATA : BEGIN OF itab5 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
xblnr LIKE bsid-xblnr,
abc LIKE bsid-wrbtr,
aaa LIKE bsid-wrbtr,
bcd LIKE bsid-wrbtr,
bbb LIKE bsid-wrbtr,
flag TYPE c,
flag1(3) TYPE c,
flag2(15) TYPE c,
sgtxt LIKE bsid-sgtxt,
bldat like bsid-bldat,
 END OF itab5.
DATA : BEGIN OF itab6 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
 xblnr LIKE bsid-xblnr,
 sgtxt LIKE bsid-sgtxt,
 bldat like bsid-bldat,
 abc LIKE bsid-wrbtr,
 aaa LIKE bsid-wrbtr,
 bcd LIKE bsid-wrbtr,
bbb LIKE bsid-wrbtr,
flag TYPE c,
flag1(3) TYPE c,
flag2(15) TYPE c,
 END OF itab6.
data : dr_deduct like bsid-wrbtr.
DATA : BEGIN OF itab7 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
xblnr LIKE bsid-xblnr,
sgtxt LIKE bsid-sgtxt,
bldat like bsid-bldat,
 END OF itab7.
DATA : BEGIN OF itab8 OCCURS 0,
 hkont LIKE bsid-hkont, " General Ledger Account
 kunnr LIKE bsid-kunnr, " Customer Number 1
 txt50 LIKE skat-txt50, " GL A/C TEXT
 dmbtr LIKE bsid-dmbtr, " Amount
 shkzg LIKE bsid-shkzg, " Debit/Credit Indication
 budat LIKE bsid-budat, " Posting date
 kostl LIKE bsid-kostl, " Cost center
 opnbl LIKE bsid-dmbtr, " Opening Balance Amount
 clsbl LIKE bsid-dmbtr, " Closing balnce Amount
 vbeln LIKE bsid-vbeln,
 blart LIKE bsid-blart,
 wrbtr LIKE bsid-wrbtr,
 bukrs LIKE bsid-bukrs,
 belnr LIKE bsid-belnr,
xblnr LIKE bsid-xblnr,
abc LIKE bsid-wrbtr,
aaa LIKE bsid-wrbtr,
bcd LIKE bsid-wrbtr,
bbb LIKE bsid-wrbtr,
flag TYPE c,
flag1(3) TYPE c,
flag2(15) TYPE c,
sgtxt LIKE bsid-sgtxt,
bldat like bsid-bldat,
 END OF itab8.
DATA : wa_ctab TYPE cust.
DATA : wa_btab TYPE invt.
DATA : wa_bsid TYPE bsid.
DATA : wai_bsid TYPE ytab.
DATA : wac_bsid TYPE ytab. " CREDIT - INVOICE
DATA : wad_bsid TYPE ytab. " DEBIT - PAYMENT
DATA : wao_bsid TYPE ytab. " ON ACCOUNT
DATA : wa_itab TYPE ftab.
DATA : ctab TYPE cust OCCURS 0.
DATA : btab TYPE invt OCCURS 0.
DATA : it_bsid TYPE bsid OCCURS 0.
DATA : iti_bsid TYPE ytab OCCURS 0. " CANCELLED INVOICES
DATA : itc_bsid TYPE ytab OCCURS 0. " CREDIT - INVOICE
DATA : itd_bsid TYPE ytab OCCURS 0. " DEBIT - PAYMENT
DATA : ito_bsid TYPE ytab OCCURS 0. " ON ACCOUNT
DATA : itab TYPE ftab OCCURS 0 with header line. " OUTPUT
DATA : inv_amt LIKE bseg-wrbtr.
DATA : paid_amt LIKE bseg-wrbtr.
DATA : cncl_amt LIKE bseg-wrbtr.
DATA : adj_amt LIKE bseg-wrbtr.
DATA : billing_date LIKE sy-datum.
DATA : overdue_date LIKE sy-datum.
DATA : overdue_days LIKE rfposx-verzn.
DATA : credit_days(4) TYPE n.
DATA : int1s(3) TYPE n VALUE 0,
 int1e(3) TYPE n VALUE 0,
 int2s(3) TYPE n VALUE 0,
 int2e(3) TYPE n VALUE 0,
 int3s(3) TYPE n VALUE 0,
 int3e(3) TYPE n VALUE 0,
 int4s(3) TYPE n VALUE 0,
 int4e(3) TYPE n VALUE 0,
 int5s(3) TYPE n VALUE 0,
 int5e(3) TYPE n VALUE 0,
 int TYPE i,
 slno(5) TYPE n VALUE 0.
CLEAR : inv_amt, ctab, btab, wa_itab, wac_bsid, wad_bsid, wao_bsid.
REFRESH : ctab, btab,itab, itc_bsid, itd_bsid, ito_bsid.
START-OF-SELECTION.
SELECT kunnr name1 adrnr FROM kna1 INTO CORRESPONDING FIELDS OF wa_ctab WHERE kunnr IN s_kunnr.
SELECT SINGLE bzirk zterm FROM knvv INTO (wa_ctab-bzirk, wa_ctab-zterm) WHERE kunnr = wa_ctab-kunnr.
SELECT SINGLE ztag1 FROM t052 INTO wa_ctab-ztag1 WHERE zterm = wa_ctab-zterm.
 WRITE : /5 WA_CTAB-KUNNR COLOR 5, WA_CTAB-NAME1 COLOR 5.
APPEND wa_ctab TO ctab.
ENDSELECT.
SELECT * FROM bsid INTO TABLE it_bsid FOR ALL ENTRIES IN ctab WHERE kunnr = ctab-kunnr
 AND budat =< key_date
 AND gjahr = fyear
 AND bukrs = ccode.
SORT it_bsid BY kunnr.
LOOP AT IT_BSID INTO WA_BSID.
IF WA_BSID-BLART = 'RV' AND WA_BSID-SHKZG = 'S' OR
 WA_BSID-BLART = 'OB' AND WA_BSID-SHKZG = 'S' or
 wa_bsid-blart = 'DR'.
 WAC_BSID-KUNNR = WA_BSID-KUNNR.
 WAC_BSID-BLART = WA_BSID-BLART.
 WAC_BSID-VBELN = WA_BSID-VBELN.
 WAC_BSID-BELNR = WA_BSID-BELNR.
 WAC_BSID-REBZG = WA_BSID-REBZG.
 WAC_BSID-WRBTR = WA_BSID-WRBTR.
 WAC_BSID-ZUONR = WA_BSID-ZUONR.
 WAC_BSID-SHKZG = WA_BSID-SHKZG.
 IF WAC_BSID-VBELN IS NOT INITIAL.
 SELECT SINGLE FKDAT FROM VBRK INTO WAC_BSID-FKDAT WHERE VBELN = WAC_BSID-VBELN.
 ELSEIF WAC_BSID-VBELN IS INITIAL.
 IF WAC_BSID-BELNR IS NOT INITIAL.
 SELECT SINGLE BuDAT FROM BSID INTO WAC_BSID-FKDAT WHERE BELNR = WAC_BSID-BELNR.
 ENDIF.
 ENDIF.
 WAC_BSID = WA_BSID.
 APPEND WAC_BSID TO ITC_BSID.
ELSEIF WA_BSID-BLART = 'DZ' AND WA_BSID-VBELN <> ' '.
ELSEIF WA_BSID-BLART = 'DZ' .
 WAD_BSID = WA_BSID.
 WAD_BSID-KUNNR = WA_BSID-KUNNR.
 WAD_BSID-BLART = WA_BSID-BLART.
 WAD_BSID-VBELN = WA_BSID-VBELN.
 WAD_BSID-BELNR = WA_BSID-BELNR.
 WAD_BSID-REBZG = WA_BSID-REBZG.
 WAD_BSID-WRBTR = WA_BSID-WRBTR.
 WAD_BSID-ZUONR = WA_BSID-ZUONR.
 WAD_BSID-SHKZG = WA_BSID-SHKZG.
 APPEND WAD_BSID TO ITD_BSID.
ELSEIF WA_BSID-BLART = 'RV' AND WA_BSID-SHKZG = 'H' AND WA_BSID-ZUONR <> ' '.
 WAI_BSID-KUNNR = WA_BSID-KUNNR.
 WAI_BSID-BLART = WA_BSID-BLART.
 WAI_BSID-VBELN = WA_BSID-VBELN.
 WAI_BSID-BELNR = WA_BSID-BELNR.
 WAI_BSID-REBZG = WA_BSID-REBZG.
 WAI_BSID-WRBTR = WA_BSID-WRBTR.
 WAI_BSID-ZUONR = WA_BSID-ZUONR.
 WAI_BSID-SHKZG = WA_BSID-SHKZG.
 APPEND WAI_BSID TO ITI_BSID.
ENDIF.
 MODIFY IT_BSID FROM WA_BSID.
ENDLOOP.
CLEAR : WAC_BSID.
LOOP AT ITC_BSID INTO WAC_BSID.
CLEAR : WAD_BSID, INV_AMT, PAID_AMT, CNCL_AMT, ADJ_AMT.
IF WAC_BSID-BLART = 'RV' AND WAC_BSID-SHKZG = 'S'.
 WAC_BSID-SINV_AMT = WAC_BSID-WRBTR.
 INV_AMT = WAC_BSID-SINV_AMT.
 READ TABLE ITD_BSID INTO WAD_BSID WITH KEY KUNNR = WAC_BSID-KUNNR VBELN = WAC_BSID-VBELN.
 LOOP AT ITD_BSID INTO WAD_BSID WHERE KUNNR = WAC_BSID-KUNNR AND VBELN = WAC_BSID-VBELN.
 IF SY-SUBRC = 0.
 WAC_BSID-PAID_AMT = WAD_BSID-WRBTR.
 PAID_AMT = PAID_AMT + WAD_BSID-WRBTR.
 ENDIF.
 ENDLOOP.
 IF PAID_AMT IS NOT INITIAL.
 WAC_BSID-BALN_AMT = WAC_BSID-SINV_AMT - WAC_BSID-PAID_AMT.
 WAC_BSID-PAID_AMT = PAID_AMT.
 WAC_BSID-BALN_AMT = WAC_BSID-SINV_AMT - PAID_AMT.
 WAC_BSID-AGE_AMT = WAC_BSID-BALN_AMT.
 ELSE.
 WAC_BSID-PAID_AMT = 0.
 WAC_BSID-BALN_AMT = WAC_BSID-SINV_AMT.
 WAC_BSID-AGE_AMT = WAC_BSID-BALN_AMT.
 ENDIF.
 LOOP AT ITI_BSID INTO WAI_BSID WHERE KUNNR = WAC_BSID-KUNNR AND ZUONR = WAC_BSID-VBELN.
 IF SY-SUBRC = 0.
 WAC_BSID-PAID_AMT = WAD_BSID-WRBTR.
 CNCL_AMT = CNCL_AMT + WAI_BSID-WRBTR.
 ENDIF.
 ENDLOOP.
 IF CNCL_AMT IS NOT INITIAL.
 WAC_BSID-BALN_AMT = WAC_BSID-SINV_AMT - WAC_BSID-PAID_AMT.
 WAC_BSID-CNCL_AMT = CNCL_AMT.
 WAC_BSID-BALN_AMT = WAC_BSID-BALN_AMT - CNCL_AMT.
 WAC_BSID-AGE_AMT = WAC_BSID-BALN_AMT.
 ELSE.
 WAC_BSID-BALN_AMT = WAC_BSID-BALN_AMT.
 WAC_BSID-AGE_AMT = WAC_BSID-BALN_AMT.
 ENDIF.
ELSEIF WAC_BSID-BLART = 'OB' AND WAC_BSID-SHKZG = 'S'.
 IF WAC_BSID-ZUONR <> ' '.
 LOOP AT ITD_BSID INTO WAD_BSID WHERE KUNNR = WAC_BSID-KUNNR AND VBELN = ' ' AND ZUONR = WAC_BSID-ZUONR.
 IF SY-SUBRC = 0.
 ADJ_AMT = ADJ_AMT + WAD_BSID-WRBTR.
 ENDIF.
 ENDLOOP.
 WAC_BSID-ADJ_AMT = ADJ_AMT.
 WAC_BSID-BALN_AMT = WAC_BSID-WRBTR - ADJ_AMT.
 WAC_BSID-AGE_AMT = WAC_BSID-BALN_AMT.
 ELSEIF WAC_BSID-ZUONR = ' '.
 WAC_BSID-BALN_AMT = WAC_BSID-WRBTR.
 WAC_BSID-AGE_AMT = WAC_BSID-BALN_AMT.
 ENDIF.
ENDIF.
 PERFORM AGING_CALCULATION.
 WA_ITAB-KUNNR = WAC_BSID-KUNNR.
 WA_ITAB-SINV_AMT = WAC_BSID-SINV_AMT.
 WA_ITAB-PAID_AMT = WAC_BSID-PAID_AMT.
 WA_ITAB-CNCL_AMT = WAC_BSID-CNCL_AMT.
 WA_ITAB-BALN_AMT = WAC_BSID-BALN_AMT.
 WA_ITAB-OD_DAYS = WAC_BSID-OD_DAYS.
 WA_ITAB-BALN1 = WAC_BSID-BALN1.
 WA_ITAB-BALN2 = WAC_BSID-BALN2.
 WA_ITAB-BALN3 = WAC_BSID-BALN3.
 WA_ITAB-BALN4 = WAC_BSID-BALN4.
 WA_ITAB-BALN5 = WAC_BSID-BALN5.
 WA_ITAB-BALN6 = WAC_BSID-BALN6.
 COLLECT WA_ITAB INTO ITAB.
MODIFY ITC_BSID FROM WAC_BSID.
COLLECT WAC_BSID.
ENDLOOP.
CLEAR : WA_ITAB, WA_CTAB.
LOOP AT CTAB INTO WA_CTAB.
CLEAR : WAO_BSID.
LOOP AT IT_BSID INTO WA_BSID WHERE KUNNR = WA_CTAB-KUNNR.
IF WA_BSID-BLART = 'RV' OR
 WA_BSID-BLART = 'OB' OR
 WA_BSID-BLART = 'DG' OR
 WA_BSID-BLART = 'DR' OR
 WA_BSID-BLART = 'DZ' OR
 WA_BSID-BLART = 'SA' OR
 WA_BSID-BLART = 'AB'.
 WAO_BSID-KUNNR = WA_BSID-KUNNR.
 WAO_BSID-BLART = WA_BSID-BLART.
 WAO_BSID-VBELN = WA_BSID-VBELN.
 WAO_BSID-BELNR = WA_BSID-BELNR.
 WAO_BSID-REBZG = WA_BSID-REBZG.
 WAO_BSID-WRBTR = WA_BSID-WRBTR.
 WAO_BSID-SHKZG = WA_BSID-SHKZG.
 WAO_BSID-ZUONR = WA_BSID-ZUONR.
 WAO_BSID-SHKZG = WA_BSID-SHKZG.
 APPEND WAO_BSID TO ITO_BSID.
 ENDIF.
ENDLOOP.
CLEAR : WAO_BSID.
LOOP AT ITO_BSID INTO WAO_BSID WHERE KUNNR = WA_CTAB-KUNNR.
IF WAO_BSID-BLART = 'OB' AND WAO_BSID-SHKZG = 'H'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_OBH = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'OB' AND WAO_BSID-SHKZG = 'S'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_OBS = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'DG'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_DG = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'DR'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT + WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_DR = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'DZ' AND WAO_BSID-SHKZG = 'H'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_DZH = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'DZ' AND WAO_BSID-SHKZG = 'S'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_DZS = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'SA' AND WAO_BSID-SHKZG = 'S'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT + WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_SAS = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'SA' AND WAO_BSID-SHKZG = 'H'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_SAH = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'AB' AND WAO_BSID-SHKZG = 'S'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT + WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_ABS = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'AB' AND WAO_BSID-SHKZG = 'H'.
 WAO_BSID-ONAC_AMT = WAO_BSID-ONAC_AMT - WAO_BSID-WRBTR.
 WAO_BSID-WRBTR_ABH = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'RV' AND WAO_BSID-SHKZG = 'H' AND WAO_BSID-ZUONR = ' '.
ELSEIF WAO_BSID-BLART = 'RV' AND WAO_BSID-SHKZG = 'H'.
 WAO_BSID-WRBTR_RVH = WAO_BSID-WRBTR.
ELSEIF WAO_BSID-BLART = 'RV' AND WAO_BSID-SHKZG = 'S'.
 WAO_BSID-WRBTR_RVS = WAO_BSID-WRBTR.
ENDIF.
 WA_ITAB-KUNNR = WAO_BSID-KUNNR.
 WA_ITAB-WRBTR_DG = WAO_BSID-WRBTR_DG.
 WA_ITAB-WRBTR_DR = WAO_BSID-WRBTR_DR.
 WA_ITAB-WRBTR_DZS = WAO_BSID-WRBTR_DZS.
 WA_ITAB-WRBTR_DZH = WAO_BSID-WRBTR_DZH.
 WA_ITAB-WRBTR_OBH = WAO_BSID-WRBTR_OBH.
 WA_ITAB-WRBTR_OBS = WAO_BSID-WRBTR_OBS.
 WA_ITAB-WRBTR_SAH = WAO_BSID-WRBTR_SAH.
 WA_ITAB-WRBTR_SAS = WAO_BSID-WRBTR_SAS.
 WA_ITAB-WRBTR_RVH = WAO_BSID-WRBTR_RVH.
 WA_ITAB-WRBTR_RVS = WAO_BSID-WRBTR_RVS.
 WA_ITAB-WRBTR_ABH = WAO_BSID-WRBTR_ABH.
 WA_ITAB-WRBTR_ABS = WAO_BSID-WRBTR_ABS.
 WA_ITAB-AC_AMT = WAO_BSID-AC_AMT.
 COLLECT WA_ITAB INTO ITAB.
MODIFY ITO_BSID FROM WAO_BSID.
ENDLOOP.
ENDLOOP.
CLEAR : SLNO.
clear : wa_itab.
SORT ITAB BY KUNNR.
LOOP AT ITAB INTO WA_ITAB.
SLNO = SLNO + 1.
WA_ITAB-SNO = SLNO.
READ TABLE CTAB INTO WA_CTAB WITH KEY KUNNR = WA_ITAB-KUNNR.
 WA_ITAB-NAME1 = WA_CTAB-NAME1.
 WA_ITAB-BZIRK = WA_CTAB-BZIRK.
 WA_ITAB-ZTAG1 = WA_CTAB-ZTAG1.
 WA_ITAB-AC_AMT = WA_ITAB-WRBTR_SAS
 - WA_ITAB-WRBTR_SAH
 - WA_ITAB-WRBTR_OBH
 + WA_ITAB-WRBTR_OBS
 + WA_ITAB-WRBTR_RVS
 - WA_ITAB-WRBTR_RVH
 - WA_ITAB-WRBTR_ABH
 + WA_ITAB-WRBTR_ABS
 - WA_ITAB-WRBTR_DG
 + WA_ITAB-WRBTR_DR
 - WA_ITAB-WRBTR_DZH
 + WA_ITAB-WRBTR_DZS.
*WRITE : / WA_ITAB-WRBTR_DR.
 data : aaaa type p decimals 2,
 bbbb type p decimals 2,
 cccc type p decimals 2,
 wrbtr_shkzg like bsid-shkzg.
SELECT shkzg wrbtr
 FROM bsid
 INTO (wrbtr_shkzg , wrbtr_note )
 WHERE kunnr = wa_itab-kunnr
 AND UMSKZ = 'G'.
 if wrbtr_shkzg = 'S'.
aaaa = wrbtr_note + aaaa.
elseif wrbtr_shkzg = 'H'.
bbbb = wrbtr_note + bbbb.
endif.
endselect.
cccc = BBBB - AAAA.
wa_itab-outs_amt = wa_itab-ac_amt.
wa_itab-onac_amt = wa_itab-baln_amt - wa_itab-outs_amt.
onacc = wa_itab-onac_amt.
wa_itab-vbeln = wac_bsid-vbeln.
WRITE : / wa_itab-sno,
 5 wa_itab-kunnr LEFT-JUSTIFIED HOTSPOT ON,
 16 wa_itab-name1,
 50 wa_itab-bzirk,
 63 wa_itab-ztag1 RIGHT-JUSTIFIED,
 69 CCCC LEFT-JUSTIFIED,
 85 wa_itab-outs_amt,
 105 wa_itab-baln1,
 125 wa_itab-baln2,
 145 wa_itab-baln3,
 165 wa_itab-baln4,
 185 wa_itab-baln5,
 205 wa_itab-baln6,
 225 wa_itab-onac_amt
MODIFY itab FROM wa_itab.
HIDE : wa_itab-kunnr , wa_itab-name1.
ENDLOOP.
WRITE : / sy-uline.
TOP-OF-PAGE.
WRITE : / 'SNo',
 5 'C-Code',
 16 'Customer Name',
 50 'Region',
 58 ' CR-DAYS',
 72 'SEC.AMOUNT',
 86 'Net O/S Amount',
 107 '0 to', int1e, 'Days',
 125 int2s, 'to', int2e, 'Days',
 145 int3s, 'to', int3e, 'Days',
 165 int4s, 'to', int4e, 'Days',
 185 int5s, 'to', int5e, 'Days',
 210 '>',int5e, 'Days',
 230 'On Account',
 / sy-uline.
 'Invoice Amount',
 80 'Paid Amount',
 100 'Balance Amount',.
FORM aging_calculation.
CLEAR : billing_date, credit_days, wa_ctab.
DATA : shiftdays TYPE tb_days_to_pos.
CLEAR : shiftdays, overdue_days.
READ TABLE ctab INTO wa_ctab WITH KEY kunnr = wac_bsid-kunnr.
billing_date = wac_bsid-fkdat.
credit_days = wa_ctab-ztag1.
 overdue_date = billing_date.
CALL FUNCTION 'FAGL_ITEM_OVERDUE_DAYS'
 EXPORTING
 key_date = key_date
 PAY_DATE =
 due_date = overdue_date
 CLEAR_DATE =
 IMPORTING
 OVER_SKONTO1_DAYS =
 overdue_days = overdue_days
 wac_bsid-od_days = overdue_days.
 IF int1 IS INITIAL.
 int1s = 0.
 int1e = 0.
 ELSEIF int1 IS NOT INITIAL.
 int1s = 0.
 int1e = int1.
 ENDIF.
 IF int2 IS INITIAL.
 int2s = 0.
 int2e = 0.
 ELSE.
 int2s = int1 + 1.
 int2e = int2.
 ENDIF.
 IF int3 IS INITIAL.
 int3s = 0.
 int3e = 0.
 ELSE.
 int3s = int2 + 1.
 int3e = int3.
 ENDIF.
 IF int4 IS INITIAL.
 int4s = 0.
 int4e = 0.
 ELSE.
 int4s = int3 + 1.
 int4e = int4.
 ENDIF.
 IF int5 IS INITIAL.
 int5s = 0.
 int5e = 0.
 ELSE.
 int5s = int4 + 1.
 int5e = int5.
 ENDIF.
 IF wac_bsid-od_days BETWEEN int1s AND int1e.
 wac_bsid-baln1 = wac_bsid-age_amt.
 ELSEIF wac_bsid-od_days BETWEEN int2s AND int2e.
 wac_bsid-baln2 = wac_bsid-age_amt.
 ELSEIF wac_bsid-od_days BETWEEN int3s AND int3e.
 wac_bsid-baln3 = wac_bsid-age_amt.
 ELSEIF wac_bsid-od_days BETWEEN int4s AND int4e.
 wac_bsid-baln4 = wac_bsid-age_amt.
 ELSEIF wac_bsid-od_days BETWEEN int5s AND int5e.
 wac_bsid-baln5 = wac_bsid-age_amt.
 ELSEIF wac_bsid-od_days > int5e.
 wac_bsid-baln6 = wac_bsid-age_amt.
 ENDIF.
ENDFORM.
please tell me how can i include blart = dr in this report for that specific period in this report
every thing except this working fine
points will be awarded

Hi,
In this way you can get the summation dr in the base list.
LOOP AT ITAB INTO WA_ITAB.
dr_total = dr_total + WA_ITAB-WRBTR_DR.
endloop.
If you want to include blart = dr in this report for that specific period what you can do is write HIDE inside loop and hide DR
Later on you can read it directly from the hide table for that specific periord and can make blart = dr.
Reward some points
Bye,
Anomitro

User-exit in va01(real time problem)

Hi Experts,
suppose that while creating a sales order i have 4 material in it.
now what i want that if the price(kbetr) of any material is below 50 then it should give a error message that 'price for this material is below 50' and that sales order can't be created.but if we delete that material from the sales order or there is no material whose value is less then 50 then we can save it.
Please help me on this issue.which user-exit should i use for it.
it give be much better if any one1 can provide me the code do it plus the name of the user-exit.
please help me out its very urgent.
necessary points will be awarded,
Thanxs In Advance,

i m trying to check the price for some conditions for every material. if any of the price is less then 50 Rs the it should gimme an error message that the SO can't be created.
i am writing code in this user-exit
FORM USEREXIT_SAVE_DOCUMENT_PREPARE
and the code is
data val type i.
SELECT KNUMH FROM A501 INTO WA_ITEM-KNUMH WHERE MATNR = VBAP-MATNR
                                                   AND   WERKS = VBAP-WERKS
                                                   and kschl = 'ZCPR'
                                                   and AUART_SD = vbak-AUART
                                                   and kunwe = vbak-kunnr.
       SELECT SINGLE kschl KBETR FROM KONp INTO (kschl ,KBETR ) WHERE KNUMH = WA_ITEM-KNUMH.
val = kbetr / 100.
CASE KSCHL.
    WHEN 'ZCPR'.
    if ( val >= 50 ).
      message 'sales order created' type 'S'.
    else.
    message 'sales order cant be created' type 'E'.
      endif.
    ENDCASE.
            ENDSELECT.
but this is only checking for the last material only.
what change should i make that it will check all material in the sales order instead of the last one

Real time tickets

Hi friends
Can any one who are in the support project can give me some of the real time problems from end users-tickets-any critical tickets with solution please
thanks & Regards
maunami

Real Time Issue:
Billing Document not released to accounting / Accounts determination:
To resolve the error, you can analyze account determination in the billing document. Process:
Goto T.Code: VF02 & Enter Invoice number
Next (On the top most strip) goto Environment
Next (Select Environment) go to Account determination
Next (In Account Determination) select Revenue Account Determination (first option)
This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.
Possible errors:
1. VKOA not maintained for required combination
Solution: Maintain the combination in VKOA.
2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).
Solution:
Option 1 (Standard solution):
step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
step 2: Maintain Customer master / Material Master correctly.
step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
Option 2:
Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.
3. Account Key not maintained in Pricing Procedure:
Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.
4. Billing Document not being released to accounting --
In Material Master, there is some link between Profit Centre & MRP Type. If one of it is not maintained, erratically few documents get stuck while releasing Billing Document to accounting. Few of course get posted.
Solution1: Cancel Billing Document --> Reverse PGI --> Cancel Delivery --> Block the sales Order & Create new sales Cycle all over again after rectifying Material master.
Solution 2: (Temporary Solution) In Debug mode in Billing, force the Profit Center in Billing Document with the help of Abaper. But ensure Material master is rectified.
From FI Side, you require to check that all the G/L account has been maintained through T.Code: FS00. G/L account being Master data has to be created in each client to upload through LSMW / SCATT / BDC.
In Billing Document in change mode (in the first screen where we enter Billing Document number), on the top most left hand corner, take a dropdown on Billing Document & select Release to accounting. Here you can get the under mentioned possible message:
1. G/L account not found
2. Cost Element not maintained for G/L account.
In both the above cases, FI consultant requires to take corrective action.
Pricing:
This is very specific & differs from client to client & may also differ based on scenario.
Write-up on Pricing -
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the necessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the necessary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Sales Document not assigned to Sales Area:
SPRO --> Sales & Distribution --> Sales --> Sales Documents --> Sales Document Header --> Assign Sales Area To Sales Document Types --> Assign sales order types permitted for sales areas (do ensure to maintain combined Sales organization, combined Distribution channel & combined division. for eg: Sales org 1000 & sales org 1000, Sales org 2000 & sales org 2000, & so on ....
similarly for distribution channel & Division, so that the Sales area combination is available for assignment to Sales Document Type.)
Issues related to Customer Master data:
1. what is the impact of leaving customer pricing procedure & customer statistic group blank in customer master --> sales area data --> sales tab:
If Customer Pricing Procedure is left blank, Pricing will not be determined.
If customer statistic group is left blank, then data will not flow to standard reports.
2. Who maintains reconciliation account in customer master?
Ideally, reconciliation account is maintained by FI person, but if SD person is authorized & has the knowledge of which reconciliation account to be maintained, then even SD person can maintain the same.
3. Terms of payment appear in Company Code Data & sales Area Data. What is the impact of each? why is it not populated automatically, once it is maintained at either field?
Terms of payment from company code data is for reporting purpose & it is from sales area data that it flows to sales order.
It is a standard feature of SAP that it is not populated automatically if maintained at either of the field, but it is a must in sales area data & can be skipped in company code data.
4. Unable to select Sales Area for Customer Master Creation?
Most Probably either sales area is not defined or customization not done for common Sales Org & Common Distribution Channel. To maintain this configuration: SPRO --> Sales & Distribution --> Master Data --> Define Common Distribution Channels / Define Common Divisions
The above are few examples.
/message/3690162#3690162 [original link is broken]
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Real time task synchronization

I am using LabVIEW real time and I want to "trigger" a lower priority task at the end of the highest priority task if it isn't already done. What is the best solution ? I have read somewhere on NI site that the synchronisation palette doesn't guarantee determinism but unfortunately the real time fifos do not provide a blocking read call. Is there a potential real time problem when using occurences ? I would just like a simple deterministic mechanism to wake up a task if it isn't already awake.
Thanks in advance.

Monsieur,
Je vous invite à consulter la doc ci-dessous pour plus d'infos sur comment LabVIEW gère les priorités lorsque plusieurs VIs s'exécutent en parallèle.
* How Does Priority Affect the Execution of VIs?
http://digital.ni.com/public.nsf/websearch/84081F249CEF7AB7862569450074168C?OpenDocument
* How is Priority of Execution Assigned when Loading and Executing Multiple VIs in LabVIEW?
http://digital.ni.com/public.nsf/websearch/44AB5BEDC20CB43C862565D4000D9885?OpenDocument
Les RT FIFOs sont le meilleur moyen pour transférer des données entre threads (typiquement, un thread critique avec un thread normal ou lower).
Les RT FIFOs ne cassent pas le déterminisme d'une application RT contrairement aux variables locales ou globales.
La gestion de l'exécution est entièrement faite par le Scheduler du moteur LabVIEW RT. Vous n'avez pas le contrôle sur son mode de fonctionnement.
Vous n'avez pas du tout intérêt à synchroniser avec les outils de LabVIEW une tâche critique RT avec une tâche non critique car vous allez forcément casser le déterminisme de l'application RT. Vous pouvez cependant synchroniser des portions de code du VI non critique (occurence pour déclencher du code sur génération d'un événement logiciel, rendez-vous pour synchro démarrage multi-VIs, sémaphores ...).
Cordialement.
Matthieu Gourssies
National Instruments

Problem with DAQmx and Real Time PCI-7041/6040E.

Problem with DAQmx and Real Time PCI-7041/6040E.
I have a problem with the Real Time card PCI-7041/6040E, I think it is properly installed because my software run with the traditional NI-DAQ. When I try to use the new DAQmx to acquire one signal, Labview doesn't see any device for de DAQ card 6040E.
Information, I work on Windows XP and LabView v7.0.0 (NIDAQ RT v7.0.0, NI-Serial RT v2.5.2, NI-VISA v3.0.1 and NI-Watchdog v2.0.0).
Could Labview RT run with new DAQmx ?
What can I do to use DAQmx with PCI-7041/6040E?
Thanks for your help !

Hello,
I refer to your posts because i am using the PCI 7041/6040E card as
well but without any success to make it work. The problem I have
already described in the following thread:
http://forums.ni.com/ni/board/message?board.id=170&message.id=120198
Would be nice if you had a look on it, maybe you can help me. BTW, the
thread starts with a problem of someone else, the difficulties I
encountered are to be found a little bit to the bottom of the thread's
page.
Thank you!
Dirk Völlger
Darmstadt
Message Edited by ratschnowski on 07-28-2005 07:14 AM

I have problem with playback in real time

playback in real time is slowly, i have BlackMagic duo decklnik card
what is the problem should i have to change the settings on the project?
My english isn't good, hope you will understand me.
Thank You.

>Is mov file 1920 x 1080
That doesn't really say much - what is the FORMAT of the media? Look at the Item Properties. Posting a screen shot of the Item Properties would help. Do the same with the Sequence Settings.
>how can i change FCP's RT settings to Dynamic.
Use the drop-down RT menu near the upper left-hand corner of the Timeline.
Also please answer the other questions:
Where is the media stored?
How is that hard drive connected to your Mac?
How much available free space on each hard drive (percentage)? Please list free space individually for each hard drive.
-DH

Standby DB real time redo log apply problem

Hi all,
I am using Oracle 10g to create physical standby db. In the standby
db, normal archived log apply does not have problem, but when I try to
use redo log real time apply and issue command
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE;
it shows:
ERROR at line 1:
ORA-38500: USING CURRENT LOGFILE option not available without stand
What is the problem??
Thanks a lot !
Steven

Note:3633226.8 from Metalink states:
Setting a standby's RealTimeApply property to ON when there are no standby
redo logs on the standby or the standby is not in SYNC transport, will
seemingly succeed. However, the apply engine will not start. The DRC log
will report an error like ORA-38500. In this case, add standby redo logs
and set the log transport mode for the standby to be SYNC and set the
standby state to ONLINE.
Workaround:
Add Standby Redo Logs on the standby and set the following broker properties
on the standby:
LogXptMode to SYNC and reset RealTimeApply to ON.
Then set the standby state to ONLINE.
HTH

TWO VERY TOUGH SUPPORT PROBLEMS FACED AND SOLVED IN REAL TIME

pls any body post two very tough support problems faced and solved in real time.
my id is: [email protected]

Hi Priya.,
For example client wants his customer legacy number in XD01 master data which is not there in Standard SAP.we can satisfy the requirement with USER EXIT
2) If the client wants customer Phone number in the sales order we can use user exit to satify the requirement
These are not provided in Standard SAP & we should work out on alternative way
REWARD if helpfull
Thanks & Regards
Narayana

Real time problems

Similar Messages

Maybe you are looking for