Functional specs for o/p type for depot sales

hi all,
can anybodey provide me with hte fuctional specs for depot sales o/p.the outgoing excise invoice is generated against the MIGO excise number. the same excise invoice number is generated against multiple deliveries. moreover there are no excise conditions in the comm invoice pricing procedure, the excise enteries are flowing from the MIGO docs.
thnx in advance
saurabh

resolved.

Similar Messages

You are given functional specs for a BDC program

You are given functional specs for a BDC program
and you need to decide whether to write a method
call transaction or a session. How u will decide?
plz explain clearly

depends of type of erro handling required and amount of data to be transfered, we can decide which is best method.
call transaction - no errorhandling, we have to write a code to show errors
sessin method - errohandling is there, locking mechanism is there.
for large amount of data , we should go for session method. for faster data transfer we can go for call transaction

Anyone written functional specs for reports?

Please explain how to write functional specs for reports in sales? How is it done? I need to be able to speak clearly in the interview so help is greatly appreciated.
Thank you.

Hi Haken,
Basically functional spec contains the functionality to be implemented.
http://www.saptechies.com/what-are-functional-specifications/
Suppose you need to write a spec for Treausry report.
Then you will write the following things( this is only for your understanding)
Treasury Report u2013 Receipts & Payments.
1.Business Requirement Study:
The Treasury Department of the Corporate Finance Division needs various information for reporting and planning. The proposed requirement would provide information in the form of movements in a number of selected GL Codes involving Customer and Vendor Reconciliation Accounts and Inter-Bank transactions.
1.1
Enhancement Title:Treasury Report u2013 Receipts & Payments
Enhancement Type: Report
Enhancement Number: 1245m
SAP Application Module:FI
Priority (H, M, L):     M     Related Documents:
1.2
End User Name(s): XYZ
Business Process Advisor:     YZX
Functional Designer: Vivek Baddula
1.3 Risk Assessment
This section will address the risk of pursuing the system development. Any unknowns such as new technology and critical dependencies should be discussed in this section.
1.4 Alternatives
If there are more than one alternative to handle the business requirement, this section should list such alternatives and the issues that may arise from implementing them. Nevertheless, the optimum alternative discussed in the design overview will be used
1.5Estimated Budget in Man-Hours
STAGE     MAN-HOURS
Design     0.00
Build     0.00
Test/Release     0.00
TOTAL     0.00
2.Selection screen fields.
BUKRS           Company Code       parameter         Mandatory
GJAHR            Fiscal Year            select options   Mandatory
BELNR            Document Number select options
SHKZG            Debit/Credit ind       parameter
DMBTR            Amt.in loc.cur.        parameter
3.Retrieval Logic:
Put the selection parameters in table u2018BSEGu2019 and retrieve the following details.
BUKRS                             Company Code
GJAHR                             Fiscal Year
BELNR                             Document Number
SHKZG                             Debit/Credit ind
DMBTR                             Amt.in loc.cur.
WRBTR                            Amount
PSWSL                             General ledger currency
HKONT                             G/L Account
3.1.     Total DMBTR of all BELNR by group and by SHKZG as H and show under the Debit Column of respective groups (Customer/Vendor/Inter-Bank).
3.2.     Total DMBTR of all BELNR by group and by SHKZG as S and show under the Credit Column of respective groups (Customer/Vendor/Inter-Bank).
3.4.     Similarly consider only those documents which have a PSWSL ne INR and show them under different group and SHKZG.
4..     Output Display::
Here we mention the format of the output and the fields need to be displayed.
This is just a sample prototype ...
Hope this will help you...
Regards,
Viveks

Functional Specs for Mapping Idocs to EDI

Hello Friends ..
Am new to world of EDI...
can any one explain ..wat do u mean by devolping functional specs for mapping IDocs to EDI..
If you can provide me with examples or if you guys can suggest any site where i can browse some material about EDI..i wud really appreciate...
Best Regards

Hi Rohan,
>>>do u mean by devolping functional specs for mapping IDocs to EDI..
you have to know which idoc fields you have to map to EDI message fields
take a look at those links:
they will show how do you map different IDOC message types to EDI messages
<b>IDOC - EDI mappings:</b>
http://www.sapgenie.com/sapedi/mapping.htm
<b>Analysis of the compatibility of EDIFACT messages in the form of SIMPL-EDI with the IDoc Interface:</b>
http://www.sapgenie.com/sapgenie/docs/SIMPL-EDI-E_ORDERS.doc
Regards,
michal

Functional specs for customer hierachy

Dear Gurus,
I need to develop functional specs for customer hierarchy.the requirement is to create a new hierarchy type and move all the existing records from the present customer hierarchy setup since the present system has lot of scrap data.for this i need to develop a functional and technical specs.can anyone please send it to me.can any one please help me here at vsapservicesatgmail.com.
thanks,
sap_consultant
Edited by: sap_consultant1234 on Dec 30, 2011 5:51 AM

Hi Utpal,
Welcome to SDN,
Being a newcomer to forum before posting the thread read the forum rules,you are asking to send the details to your mail which is forbidden by the forum.
Coming to the thread Customer Hierarchies stored in table KNVH,go to SE16N give the table KNVH get valid inputs and build
valid logic.
Regards
Ram

Functional specs for output of ship and debit contract

Hi All,
Does anyone have a doc on the functional specs for output of ship and debit contract? If so pls email me at [email protected]
With Thanks & Warm Regards
SK

What is the exact info which you are looking for regarding ship and debit contract?. What do you mean by functional specs..?.

Functional specs for BDC

Kindly can ayone helo me out in prepare Functional specs for BDC For f-28

Hi
There is no need of preparing FS (Functional Specs) for BDC.
You can Record the BDC and just give the Recording Name to the ABAP Guy, he will prepare the BDC based on that recording.
Go to SHDB and do the Recording.
Regards
Venkat

Functional specs for Open BI reports

Hi
Has anyone written functional specs BI report. Can you help me out with an example?
Thanks
Tarang

Hi Tarang,
I never got an oppertunity to developed a Functional Spec for BI to my knowledge it is not a big deal to prepare it.
Here we go you must be having atleast what you want from R/3 or the Functional Spec from Functionl req.
That will contain the R/3 Fields and Table names, so based on that you have to find which app area does it comes.
Then from there by seeing the fields and cross checking the Datasourcess under that application you can decide the the data source.
Once the data source is decide you can prepare the Gap analisys to proceed further.
By above details you can prepare a Functional Come Tech Spec.We made all these kind of specification(Functional Come Technical Spec).
I believe there is no saparate Functiuonal Spec for BW activities.
Best Regards,
VNK.

Functional spec for STO

Hi
Could some one provide functional spec for a( STO) z report to fetch below data .
Receving point
ship to party
STO number
Material number
delivery creation date
quantity in storeage location

Dear Rajakumar Reddy,
Your client/company will be having a format for FS.
In that FORMAT, give your inputs for STO Report based on the following points.(as i dont have system access now, check yourself before concluding. to find the table and fields, you have to press F1 on the value in the screen)
Receving point - in ME22N/ME23N, put the mouse over the receiving plant and press F1. You will get the table and field.
ship to party - in LIKP check for KUNNR/KUNAG
STO number in LIKP check for VBELN
Material number - in LIPS check for MATNR
delivery creation date- in LIKP check for DATE
quantity in storeage location - GET THE TABLE FOR MMBE and input the material and storage location to fetch QTY.
Thanks & Regards,
Hegal K Charles

FUNCTIONAL SPEC FOR GL BALANCES

THere is a functional spec for LSMW for uploading gl balances thru FB01. There are feilds like legacy account, sub account and other fields that the business user wants to flow into SAP. But in FB01 there is only one reference field which i have used for legacy account number. How do we create additional fields in FB01 in order to input other fields like legacy sub accounts and other info that would flow into SAP.
I was told to work with crosswalk tables. WHat are they and how do I use them here. Please provide detailed instructions on how to bring in additional fields from legacy into FB01
Thanks

Lakshmi, can you please send me the format of that func spec, if possible?

Functional Spec for Purchase Order Layout Sample

Hi,
Can somebody please assist me with a sample Functional spec. for defining a PO form/ layout?
Thanks

Hi
yes usually customers ask to adopt the same layout as they are already using. Usually I draw the layout on visio and assign a number for each field. In the spec I put the layout picture and and mention for which field where data will come from.
For example:
A. PO header:
Field number | Description | Source
1 | PO number | EKKO-EBELN
2 | Vendor code | EKKO-LIFNR
3 | Vendor name | LFA1-NAME1 * rule 1
C. Rules:
1 - select NAME1 from table LFA1 where LFA1-LIFNR = EKKO-LIFNR
Hope this helps.
Regards
Eduardo Chagas

Regarding Creating Functional Specs for BI project

Hi Gurus,
I am looking for some documents on "Creating Functional Specs for BI project", as my prokect is in the initial stage.
Hence we require to collect relevant info for implementing the FI-CO, SD & MM with BI project.
I will be assigning points.
My ID is: [email protected]
Thank you.
Regards,
Pradeep Kandepu
Edited by: pradeep kandepu on May 30, 2008 7:32 AM

HI shanbhu
can u please send those document to me also..
and if you hace send me the Technical spec also
My id is [email protected]
Edited by: Bramhananda Reddy on Jun 7, 2008 4:31 PM
Edited by: Bramhananda Reddy on Jun 7, 2008 4:31 PM

Re:Functional Specs for BI project respectively is-retail

Hi Gurus,
I am looking for some documents on "Creating Functional Specs for BI project", as my prokect is in the initial stage.
Hence we require to collect relevant info for implementing there (spectively is-retail )FI-CO, SD & MM with BI project.
I will be assigning points.
My ID is: [email protected]
Thank you.
Regards,
Pradeep Kandepu
Edited by: pradeep kandepu on Jun 8, 2008 5:30 PM

Hi,
Check this link,
[Functional & Tech specs;
Hope this helps you.

Pricing procedure for Depot Sales(CIN Version)

HI,
Can anyone explain me TAXINJ and
The Pricing procedure for Depot Sales(CIN Version)
alongwith the Condition Types like JMOD,JECS,JECX etc.
Points will be given
Regrds,
Binayak

Hi Binayak.
JMOD is a FI Tax condition which gets the Basic Excise duty from calculation formula 352. JEX2 is a copy of JMOD and is a Sales pricing condition. The value of JEX2 gets posted for Excise account key. This ensures that the cost accounting of excise value paid is done correctly. In cases where commercial invoice is created after utilization the condition value formula 353 ensures that the actual MODVAT utilized is accounted as excise.
Similarly JAED is a FI Tax condition which gets the Additional Excise duty from calculation formula 352. JEXA is a copy of JAED and is a Sales pricing condition. The accounting is done for the value of JEXA.
JSED is a FI Tax condition which gets the Special Excise duty from calculation formula 352. JEXS is a copy of JSED and is a Sales pricing condition. The accounting is done for the value of JEXS.
JCES is a FI Tax condition which gets the CESS from calculation formula 352. JCED is a copy of JCES and is a Sales pricing condition. The accounting is done for the value of JCED.
So, Conclusion :---->
JMOD -- > Basic Excise duty condition for FI side.
corresponding to it,
JEX2 is the Basic Excise duty condition for SD side.
That's why
account key to JMOD is linkes in TAXINJ.
and
account key to JEX2 is linkes in JDEPOT.
Hope this certainly helps you.
Please reward points if found useful to you.
Let me know if you have any other doubt.
Regards,
Gaurav Raghav.

Excise invoice for depot sale

Friends,
While creating excise invoice using J1IJ for depot sale we are getting error as "you are not authorised to create".
Ple guide.
Edited by: shiv on Jan 9, 2009 10:42 AM

Dear Shiv
Do the following once you see the message at the bottom.
In white top box, input /nsu53.
Now from top menu bar, click on System -- List -- Send. Sometimes, this Send tab will be in grey mode. In that case, at left corner, you can see a tab "Text View". Click that. Again click from top "System -- List -- Send and send a mail to your basis team.
thanks
G. Lakshmipathi

Functional specs for o/p type for depot sales

Similar Messages

Maybe you are looking for