Creation of Field Catelogue & Con. table in Tax Procedure

Hi,
We want to add new filed " Storage Location" & make condition table witht his filed catelogue. Accoridngly we want to add this in acess sequence.
We want to make a table with Plant / Material / Vendor / Storage location combination. With the same combination of vendor / Plant / Material some times we receive material directly & some times we asked 1st vendor to send the material to another vendor without receiving into our factory.
1st case it will be cenvatable & in 2nd case it is non cenvatable (2nd vendor who receives material will claim)
We maintain "Storage location" infiled catalogue VOK0 & then maintain in KOMPAZ appendix structure, so that it update KOMP & KOMK tables accordingly. When we are creating new table with storage location, we are getting error i.e. "storage location" field is not updated in KOMP & KOMK tables.
Can u guide me how to proceed ?
Regards
Sai Krishna

Hi,
In standard SAP, we can create any new field catelogue in TAXINN, we have to choose from exisitng fields only.
Regards
Sai Krishna

Similar Messages

Update Yes/No field in access table through oracle procedure

Hi,
How to update Yes/No field in access table through oracle procedure. all other fields like AutoNumber, Text I can update it. Yes/No field how to update? Please, any one can help me?
Thanks and Regards,
Sudha.

Sudha Teki wrote:
select "fldPost" from tblPHd@ODBCLNKNot quite sure what you mean, but the way you select the column would indicate a case sensitive column name
Look at this example
SQL> create table t
2 ("this" varchar2(10))
3 /
Table created.
SQL> insert into t values ('hello')
2 /
1 row created.
SQL> select *
2    from t
3 /
this
hello
SQL> select this
2    from t
3 /
select this
ERROR at line 1:
ORA-00904: "THIS": invalid identifier
SQL> select "this"
2    from t
3 /
this
helloIs your column name also case sensitive?

Number of fields in the table

Hi experts,
How do you obtain the number of fields of a particular table ?
I want the count of the fields of a table.
Thanks in advance,
Chithra.

Check the code below:
DATA: d_ref TYPE REF TO data,
i_alv_cat TYPE TABLE OF lvc_s_fcat,
ls_alv_cat LIKE LINE OF i_alv_cat,
fname TYPE fieldname,
ncomp(9) TYPE n,
rcount(9) TYPE n,
fcount(3) TYPE n.
TYPES: BEGIN OF itab1,
message(50) TYPE c,
END OF itab1.
DATA: g_itab1 TYPE STANDARD TABLE OF itab1.
DATA: wa_itab1 TYPE itab1.
ncomp = 1.
rcount = 0.
TYPES: tabname LIKE dcobjdef-name,
fieldname LIKE dcobjdef-name.
PARAMETER: p_tablen TYPE tabname. "Input table field
DATA: BEGIN OF itab OCCURS 0.
INCLUDE STRUCTURE dntab.
DATA: END OF itab.
FIELD-SYMBOLS : <f_fs> TYPE table,
<f_fs2> TYPE ANY,
<f_fs3> TYPE ANY,
<f_fs4> TYPE ANY.
REFRESH itab.
CALL FUNCTION 'NAMETAB_GET' "Fetches the fields
EXPORTING
langu = sy-langu
tabname = p_tablen
TABLES
nametab = itab
EXCEPTIONS
no_texts_found = 1.
LOOP AT itab .
ls_alv_cat-fieldname = itab-fieldname.
ls_alv_cat-ref_table = p_tablen.
ls_alv_cat-ref_field = itab-fieldname.
ls_alv_cat-seltext = itab-fieldtext.
ls_alv_cat-reptext = itab-fieldtext.
APPEND ls_alv_cat TO i_alv_cat.
fcount = fcount + 1.
ENDLOOP.
WRITE:/ fcount.
WRITE: ' number of column'.
internal table build
CALL METHOD cl_alv_table_create=>create_dynamic_table
EXPORTING
it_fieldcatalog = i_alv_cat
IMPORTING
ep_table = d_ref.
ASSIGN d_ref->* TO <f_fs>. " Dynamic table creation with fields of the
*table
DATA: l_field TYPE fieldname,
l_field1 TYPE fieldname.
SELECT * FROM (p_tablen) INTO CORRESPONDING FIELDS OF TABLE <f_fs>.
"Fetching of the data from the table
rcount = 0.
LOOP AT <f_fs> ASSIGNING <f_fs2>.
rcount = rcount + 1.
DO fcount TIMES.
"Here u can check the validations and process
ASSIGN COMPONENT ncomp OF STRUCTURE <f_fs2> TO <f_fs4>.
IF NOT <f_fs4> IS INITIAL.
MOVE <f_fs4> TO l_field1.
ncomp = ncomp + 1.
ELSE.
CONCATENATE 'IN ROW' rcount 'COLUMN' ncomp 'IS BLANK' INTO wa_itab1.
APPEND wa_itab1 TO g_itab1.
ncomp = ncomp + 1.
ENDIF.
ENDDO.
CLEAR:ncomp.
ENDLOOP.
LOOP AT g_itab1 INTO wa_itab1.
WRITE:/ wa_itab1 'is blank'.
ENDLOOP.
regards
Kannaiah

Tax Procedure Edit

Hi,
We need to edit field value of "J 1ICAT1AP" in " J_1IEXCDEF" table for tax procedure TAXINJ.
How we can do this.
Thanks,
Vikas Rander

Hi,
Go to SPRO > Logistics - General > India > Basic Settings > Determination of Excise Duty > Maintain Excise Defaults

MM pricing Tax procedure

Dear All,
There is no tax on purchase. Whatever tax mentioned in the invoice are capitalized/booked under expenses. Should i use FI Tax procedure for it. The illustrative pricing is as follows:
Please suggest an approach for it
Price of item          1000
Sub Total          1000
P & F @2 %          20
Sub Total          1020
Excise Duty @8%          81.6
E Cess@2%          1.63
HE Cess @1%          0.82
Sub Total          1104.05
VAT/Sales Tax /CST as applicable (Say 12.50%)          138.01
Surcharge on VAT @5%          6.90
Sub-Total          1248.95
Freight          Nil
Octroi          Nil
Insurance          Nil
Sub-Total          1248.95
Discount if any          Nil
Total          1248.95

Hi,
MM Pricing Procedure and Tax Procedure are entirely different concepts. In your example you have mentioned about excise duty, education cess and higher education cess, VAT etc. is nothing but tax. Material price, packaging and forwarding charges and discount are nothing but pricing conditions.
MM Pricing Procedure
The Basic thing is Condition Technique. In which there are
1. Access Sequence (M/07) 2. Condition Record (MEK1) 3. Condition Type (M/06) 4. Condition Table.
Tax Procedure
1. Access Sequence (OBQ2) 2. Condition Types (OBQ1) 3. Procedure (OBQ3) 4. Condition Records (FV11)
- Saleel

Table for tax fields in Purchase order

HI
I want to know in which table the taxes will go and store in purchase order .
In purchase order invoice tab there is Tax code field will be there say for example it is M1 . and if i click on the taxes adjacent to that i will get a new page or table where all the taxes is maintained for that particular M1 . Now i want to know in which table that will be stored
Regards
N.M.Pradeep kumar

HI
use
KONV
KONP
KOMV
T007*
Excise Duty - Table J_1IMATEXP ,J_1IMTCHID
for Tax - Table BSET
Tax table
regards
kunal
award if helpful

How to add additional field into output table for RFIDYYWT(Generic Withholding Tax Reporting)

Hi Experts,
How to add additional field into output table VENDORS/WH TAX TYPES AND CODES in RFIDYYWT(Generic Withholding Tax Reporting).
I have no idea how to start with, please give some advice.
Thanks!
Ice

Dear Ice,
Use Append structure, see given link:
https://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eb61446011d189700000e8322d00/content.htm
Regards,
Abbas.

TABLE FOR TAX CODE and amount break up when PO created

Hi,
Could you please tell us the table which stores the amount break up for a condiion type based on tax code when a Purchase Order is created.
Like :
When the amount (kwert) for a condition type(kschl) is 100.
Based on tax code(mwskz) and condtion type(kschl) the amount will break up
into some 60 and 40 .So this break up amount will store in some tables.
we have tried KONV .
where only 100 is stored

Hi
Pass the MWSKZ, KSCHL and ALAND fields to the table A003 table, if not A003 some A* table check that.
take the KNUMH field from it.
pass this field to KONP table along with KSCHL codn type field
You will get the condition type based amount fields from KONP (KWERT field)
Reward points if useful
Regards
Anji

Table for taxes

Hi
Can any one please suggest me (a MM guy) a table equivalent to BSET (for taxes) which will contains fields accounting document number, fiscal year, company code, material number, cost center (split account assigned vendor invoice), tax amount, and base amount for the tax amount
BSET will have all the fields except the material number and cost center. I want to know, to which material, this tax amount has been paid
waiting for your quick reply
regards
srini

Hi Srini,
refer these tables:
T005S - Taxes- Region (Province) Key
T005U - Taxes- Region Key- Texts
T006 - Units of Measurement
A003 - Tax Indicator
A053 - Taxes via Jurisdiction Code
T007A - Tax Keys
T007B - Tax Processing in Accounting
T007S - Tax Code Names
T030K - Tax Accounts Determination
T030R - Rules for Determination of Standard Accounts
T050T - General texts
T681A - Conditions: Applications
T681B - Conditions: Applications:
Texts - T681V Conditions: Usages
T681W - Conditions: Usage: Texts
T681Z - Conditions: Dependent Data for Application/Usage
T682I - Conditions: Access Sequences (Generated Form)
T683S - Pricing Procedure: Data
T683T - Pricing Procedures: Texts
T685 - Conditions: Types
T685A - Conditions: Types: Additional Price Element Data
T685T - Conditions: Types: Texts
TTXD - Description of Tax Jurisdiction Code Structure
TTXJ - Check Table for Tax Jurisdiction
TTXJT - Text Table for Tax Jurisdiction
Thanks and regards

Adding new field in customized table ZPM_QMEL_EXT

Hi all,
My requirement is to add a new field in ZPM_QMEL_EXT table numeric field no of months due (ZZ_CO_MON_DUE) .
Its value will be calculated as the # of invoices that were paid vs. what has not been paid and then from there, value of this field will be fetched.It has to be populated during the time of notifcation screen entry (iw51). The logic will be similar to this
SELECT FAEDN FROM DFKKOP INTO TABLE IT_DU_DT
                              WHERE GPART EQ WA_QMEL-KUNUM AND
                                    VKONT EQ WA_QMEL-ZZ_VKONT.
    SORT IT_DU_DT BY FAEDN ASCENDING.
    READ TABLE IT_DU_DT INTO WA_DU_DT INDEX 1.
    MOVE WA_DU_DT-FAEDN TO DUE_DT.
    CALL FUNCTION 'HR_MONTHS_BETWEEN_TWO_DATES'
      EXPORTING
        I_DATUM_BIS = SY-DATUM
        I_DATUM_VON = DUE_DT
      IMPORTING
        E_MONATE    = NO_MT.
    IF NO_MT IN P_DU_MT.
      WA_QMEL-DUE_MONTHS = NO_MT.
Awaiting your kind help .
Thanks
hariom.

Hi,
There is only one option to include extra field for standard tables that is Append Structure other than we don't have any option.
For Customizing tables we can use Append structure as well as Include Structure.
Rules: Append Structure should be in last in Field column but include structure you can insert in any where it means between the fields.
Delivery class option and data class will take care automatically while upgrading the sap system one version to Another version.(upgrading).
For that you should maintain the those properties when data base table creation.
i hope the above information may helpful to you.
Best Regards
Sreenivas Pachva

Linkage for RSEG and BSIS tables for tax item

Hi,
How to find corresponding tax line item in BSIS or BSAS table for a RSEG line item.
In case of BSET table I could find the linkage by BSET-TXGRP and RSEG-BUZEI.

The obvious link I can see is on bukrs/belnr/buzei/mwskz fields.
All available in all tables. The company code and accounting document number is normally enough but if there are multiple line items use the buzei fields as well. The tax field on is MWSKZ.
Same on both BSIS/BSAS and RSEG.
BSAS is almost the same table as BSIS but has the clearing items as well.
Message was edited by: Barry Neaves

Field exit for checking if tax number is unical in vendor master.

Hi,
is there a field exit that checks if tax number is unical in vendor master?
Best regards

Swamy,
As you've pointed out, you already know that path. I'd recommend stating all that you've already tried and ruled out while posting a query here. It'll help people putting in effort that won't be helpful to you.
Coming back to your query, there is obviously no way to introduce email ID as a sensitive field. However, there's nothing stopping you from using a little creativity here. This solution is not exactly direct, but I believe it is achievable. Here are your components:
Have a look at enhancement SAPMF02K (t.code SMOD). Look at the component FM - EXIT_SAPMF02K_001.
From table LFA1, get LFA1-ADRNR. Go to table ADR6 (SMTP Numbers (Business Address Services)).
In ADR6, field SMTP_ADDR is email ID.
You can designate a field you don't currently use as always = email ID field content on vendor master screen. This proxy field can get it's value inside the user exit I've mentioned above, and you can find the email ID using the logic I've mentioned above. Ensure that this proxy field can be designated a sensitive field. That's it!
Now, everytime a user changes the email ID, your proxy field gets changed, and thus invokes the Senstive Field rule.
I've not used this myself, but believe it should work.
Remember to assign points if found useful.
Regards
Gulshan

Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

Good day to all of you!
I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
Any help, pls?
Good day and thank you!

Hi Alex,
In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
and
Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
      1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
      2. Enhancing online maintenance in customized material master maintenance:
      Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
      In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
      If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
      Application examples for standard field selection:
      The field is mandatory and is to be flagged with a "?".
      The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
      The following data is required for each field:
            a) Field name        (T130F-FNAME)
            b) Field selection group (T130F-FGRUP)
            Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
            You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
            Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
            c) Maintenance status (T130F-PSTAT)
            List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
            d) Reference        (T130F-KZREF)
            This indicator must be set if the field from the reference material should be proposed during creation with reference.
Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
In addition, you must not add new standard fields to table T130F.
      3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
      Add the fields to central field table T130F (see above).
      Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
      Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
      For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
      If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
      Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
      As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
            a) Add the customer-specific fields to include CI_MMH1.
            The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
            Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
            b) Activate include CI_MMH1.
            c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
            d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
check this link. It may helps you to solve your issue.
Thanks
Sravan

Table of tax amt in purchase order

Hi,
what is the table for tax amt & net amt in purchase order.
thnx.

hi
for excise check table J_1IEXCHDR for header
J_1IEXCDTL for item excise
The Table name used to find the Tax Values are
KOMV: Pricing Communications-Condition Record
KONV: Conditions (Transaction Data)
From the above tables you can refer the fields below.
KAWRT
KBETR
Fetch the corresponding records based on the field
KNTYP
regards
kunal

I NEED FIELDS FROM VBFA TABLE

HI ALL,
I NEED FIELDS FROM VBFA TABLE
THE FIELDS I WANT IS :
CUSTOMER-ID
CUSTOMER NAME
CONTACT NAME
PROJECTID
ORDER NO
SALES MAN ID
ORDER PROCESS DATE
INVOICE DATE
GROSS AMOUNT
NET AMOUNT POSTAL CODE.
THANKS & REGARDS,
R.VINOD.

Hi Vinod..
Try this Code. I made all the modifications in your code .. It will solve ur issues..
REPORT zsdr_omvsa40.
TYPE-POOLS
TYPE-POOLS: slis.
TABLE DECLARATIONS
TABLES : vbak, vbkd,
zzvbak,
kna1, vbrk, vbrp, knvp .
INTERNALTABLE DECLARATION *
DATA: BEGIN OF i_vbak OCCURS 0,
vbelv LIKE vbfa-vbelv, " Sales Order no
vbeln like vbfa-vbeln, "Invoice No
erdat LIKE vbak-erdat, " Date on Which Record Was Created
kunnr LIKE vbak-kunnr,
ps_psp_pnr LIKE vbak-ps_psp_pnr, " Work Breakdown Structure Element
END OF i_vbak.
*DATA : BEGIN OF i_zzvbak OCCURS 0,
*vbeln LIKE zzvbak-vbeln,
*zssidc LIKE zzvbak-zssidc, "Salesman ID
*END OF i_zzvbak.
DATA : BEGIN OF i_vbrk OCCURS 0,
vbeln LIKE vbrk-vbeln,
fkdat LIKE vbrk-fkdat, "Invoice Date
END OF i_vbrk.
DATA : BEGIN OF i_kna1 OCCURS 0,
kunnr LIKE kna1-kunnr , " Customer Number 1
name1 LIKE kna1-name1, " Customer Name
pstlz LIKE kna1-pstlz , " Postal Code
END OF i_kna1.
DATA : BEGIN OF i_vbrp OCCURS 0,
vbeln LIKE vbrp-vbeln,
aubel LIKE vbrp-aubel,
netwr LIKE vbrp-netwr , " Net Value in Document Currency
kzwi1 LIKE vbrp-kzwi1, " Subtotal 1 from pricing procedure for condition
erdat LIKE vbrp-erdat, "Billing document.
END OF i_vbrp.
DATA : BEGIN OF i_knvp OCCURS 0,
parvw LIKE knvp-parvw , " Partner Function
kunnr LIKE knvp-kunnr ,
parnr LIKE knvp-parnr , " Number of contact person
END OF i_knvp .
DATA : BEGIN OF i_data OCCURS 0,
erdat LIKE vbak-erdat, " Date on Which Record Was Created
vbeln LIKE vbak-vbeln, " Sales Order no
fkdat LIKE vbrk-fkdat, " Invoice date.
kunnr LIKE kna1-kunnr , " Customer Number
ps_psp_pnr LIKE vbak-ps_psp_pnr, " Work Breakdown Structure Element
name1 LIKE kna1-name1, " Customer Name
netwr LIKE vbrp-netwr , " Net Value in Document Currency
kzwi1 LIKE vbrp-kzwi1, " Subtotal 1 from pricing procedure for condition
parvw LIKE knvp-parvw , " Partner Function
parnr LIKE knvp-parnr , " Number of contact person
*zssidc LIKE zzvbak-zssidc, "Salesman ID
pstlz LIKE kna1-pstlz , " Postal Code
END OF i_data.
ALV Declaraton
DATA: fieldcatalog TYPE slis_t_fieldcat_alv WITH HEADER LINE,
gd_tab_group TYPE slis_t_sp_group_alv,
gd_layout TYPE slis_layout_alv,
it_listheader TYPE slis_t_listheader,
gd_repid LIKE sy-repid.
Selection - Screen
SELECTION-SCREEN : BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS creation FOR vbak-erdat . " Sales Order Date
SELECT-OPTIONS period FOR vbrk-fkdat . " Invoice Date
SELECT-OPTIONS order FOR vbak-vbeln . " Sales order no
SELECT-OPTIONS name FOR kna1-name1 . " Customer Name
SELECT-OPTIONS contact FOR knvp-parnr . " Contact Name.
*SELECT-OPTIONS ssid FOR zzvbak-zssidc . " Salesman ID
SELECT-OPTIONS project FOR vbak-ps_psp_pnr . " Work Breakdown Structure Element
SELECTION-SCREEN : END OF BLOCK b1.
START-OF-SELECTION
START-OF-SELECTION.
PERFORM data_retrieval.
PERFORM build_fieldcatalog.
PERFORM BUILD_LAYOUT.
PERFORM top_of_page.
PERFORM fill_listheader USING it_listheader.
PERFORM display_alv_report.
END-OF-SELECTION.
*TOP-OF-PAGE.
TOP-OF-PAGE.
END-OF-PAGE.
*& Form BUILD_FIELDCATALOG
text
FORM build_fieldcatalog.
fieldcatalog-fieldname = 'KUNNR'.
fieldcatalog-seltext_m = 'Sold to Party'.
fieldcatalog-col_pos = 0.
fieldcatalog-outputlen = 10.
fieldcatalog-emphasize = 'X'.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'NAME1'.
fieldcatalog-seltext_m = 'Hlev Customer'.
fieldcatalog-col_pos = 1.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'PARNR'.
fieldcatalog-seltext_m = 'Contact name'.
fieldcatalog-col_pos = 2.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'PS_PSP_PNR'.
fieldcatalog-seltext_m = 'Project ID'.
fieldcatalog-col_pos = 3.
fieldcatalog-do_sum = 'X'.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'VBELN'.
fieldcatalog-seltext_m = 'Sales Document Type'.
fieldcatalog-col_pos = 4.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'ZSSIDC'.
fieldcatalog-seltext_m = 'SSID'.
fieldcatalog-col_pos = 5.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'ERDAT'.
fieldcatalog-seltext_m = 'so date'.
fieldcatalog-col_pos = 6.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'FKDAT'.
fieldcatalog-seltext_m = 'inv date'.
fieldcatalog-col_pos = 7.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'KWZI1'.
fieldcatalog-seltext_m = 'gross amt'.
fieldcatalog-col_pos = 8.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'NETWR'.
fieldcatalog-seltext_m = 'net amt'.
fieldcatalog-col_pos = 9.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
fieldcatalog-fieldname = 'PSTLZ'.
fieldcatalog-seltext_m = 'Postal code'.
fieldcatalog-col_pos = 10.
APPEND fieldcatalog TO fieldcatalog.
CLEAR fieldcatalog.
ENDFORM. "BUILD_FIELDCATALOG
*& Form DATA_RETRIEVAL
text
FORM data_retrieval.
SELECT VBFAvbelv VBFAvbeln
         VBAKerdat VBAKkunnr VBAK~ps_psp_pnr
         INTO TABLE i_vbak
FROM VBFA
INNER JOIN vbak
ON VBFAVBELV = VBAKVBELN
WHERE VBAK~erdat IN creation
AND VBFA~vbelV IN ORDER
AND VBAK~ps_psp_pnr IN project
AND VBFA~VBTYP_N = 'M' "Subsequent doc is Invoice
AND VBFA~VBTYP_V = 'C' "Prec doc is Sales order
IF NOT i_vbak[] IS INITIAL.
**Change of ORDER in SELECTS HERE
    SELECT vbeln fkdat FROM vbrk INTO TABLE i_vbrk
    FOR ALL ENTRIES IN i_vbak
    WHERE vbeln = i_vbak-vbeln
    AND fkdat IN period.
    IF NOT i_vbrk[] IS INITIAL.
      SELECT vbeln aubel netwr kzwi1 FROM vbrp INTO TABLE i_vbrp
      FOR ALL ENTRIES IN i_vbrk
      WHERE VBELN = i_vbrk-vbeln.
    endif.
    SELECT kunnr name1 pstlz FROM kna1 INTO TABLE i_kna1 FOR ALL ENTRIES IN i_vbak
    WHERE kunnr = i_vbak-kunnr
    AND name1 IN name.
*SELECT vbeln zssidc FROM zzvbak INTO TABLE i_zzvbak FOR ALL ENTRIES IN i_vbak
*WHERE vbeln = i_vbak-vbeln
*AND zssidc IN ssid .
select netwr kzwi1 erdat from vbrp into table i_vbrp for all entries in i_vbak
where erdat = i_vbak-erdat.
    SELECT kunnr parnr parvw FROM knvp INTO CORRESPONDING FIELDS OF TABLE i_knvp FOR ALL ENTRIES IN i_vbak
    WHERE kunnr = i_vbak-kunnr
    AND parvw = 'AP'
    AND parnr IN contact.
ENDIF .
SORT I_VBAK BY VBELN .
SORT I_VBRK BY VBELN .
LOOP AT i_vbrp. "Invoice Item data
    MOVE i_vbrp-netwr TO i_data-netwr .
    MOVE i_vbrp-kzwi1 TO i_data-kzwi1.
    READ table I_VBAK WITH KEY VBELN = I_VBRP-VBELN BINARY SEARCH. "Sales Order info
    IF SY-SUBRC = 0.
      MOVE I_VBAK-VBELV TO I_DATA-VBELN.   "Sales Order no
      MOVE I_VBAK-erdat TO I_DATA-erdat.   " Date on Which Record Was Created
      MOVE I_VBAK-kunnr TO I_DATA-KUNNR.    "Customer No
      MOVE I_VBAK-ps_psp_pnr TO I_DATA-ps_psp_pnr. " Work Breakdown Structure Element
    endif.
    READ TABLE I_VBRK WITH KEY VBELN = I_VBRP-VBELN BINARY SEARCH.   "Invoice header info
    IF SY-SUBRC = 0.
      MOVE i_vbrk-fkdat TO i_data-fkdat.
    endif.
    READ TABLE I_KNA1 WITH KEY KUNNR = I_VBAK-KUNNR BINARY SEARCH.   "Customer info
    IF SY-SUBRC = 0.
      MOVE i_kna1-kunnr TO i_data-kunnr.
      MOVE i_kna1-name1 TO i_data-name1.
      MOVE i_kna1-pstlz TO i_data-pstlz .
    endif.
    READ TABLE I_KNvp WITH KEY KUNNR = I_VBAK-KUNNR BINARY SEARCH.   "Partner info
    IF SY-SUBRC = 0.
      MOVE i_knvp-parnr TO i_data-parnr.
    endif.
    APPEND i_data.
ENDLOOP.
ENDFORM. "DATA_RETRIEVAL
*& Form DISPLAY_ALV_REPORT
text
FORM display_alv_report.
GD_REPID = SY-REPID.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER = ' '
I_BUFFER_ACTIVE = ' '
i_callback_program = sy-repid
I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
i_callback_top_of_page = 'TOP_OF_PAGE'
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
I_STRUCTURE_NAME =
I_BACKGROUND_ID = ' '
I_GRID_TITLE =
I_GRID_SETTINGS =
IS_LAYOUT =
it_fieldcat = fieldcatalog[]
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
IT_EVENT_EXIT =
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
I_HTML_HEIGHT_TOP = 0
I_HTML_HEIGHT_END = 0
IT_ALV_GRAPHICS =
IT_HYPERLINK =
IT_ADD_FIELDCAT =
IT_EXCEPT_QINFO =
IR_SALV_FULLSCREEN_ADAPTER =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
TABLES
t_outtab = i_data.
EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2 .
*IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
*ENDIF.
ENDFORM. "DISPLAY_ALV_REPORT
FORM FOR FILLING LISTHEADER *
FORM fill_listheader USING it_listheader TYPE slis_t_listheader.
DATA : wa_listheader TYPE slis_listheader.
wa_listheader-typ = 'H'.
wa_listheader-info = 'Noel Gifts International Limited '.
APPEND wa_listheader TO it_listheader.
wa_listheader-typ = 'S'.
wa_listheader-info = 'CUSTOMER CREDIT EXCEPTION REPORT' .
APPEND wa_listheader TO it_listheader.
CLEAR wa_listheader.
ENDFORM. "fill_listheader
*& Form top_of_page
text
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary = it_listheader.
ENDFORM. "top_of_page
REWARD IF HELPFUL.

Creation of Field Catelogue & Con. table in Tax Procedure

Similar Messages

Maybe you are looking for