<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884383#M933306</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi narayana&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;i think u need to write a driving program and a provided with a smatform u sit along with the SD consultant. &lt;/P&gt;&lt;P&gt;ur further views can be shared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgs,&lt;/P&gt;&lt;P&gt;Venkat.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 May 2008 14:26:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-28T14:26:02Z</dc:date>
    <item>
      <title>ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884382#M933305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;THIS IS MY URGENT REQUIREMENT ...&lt;/P&gt;&lt;P&gt;I DONT KNOW ABAP QUERY PROGRAM ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PLEASE SUGGEST ME A WAY ON THIS ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functional requirements&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Introduction&lt;/P&gt;&lt;P&gt;The wish of the customer is a printable customer overview. All desired fields will be shown in a new query called ZZADDRSS_CO. Double entries are taken for granted because of the data taken from the sales area and because of multiple contact persons. The customer accepts this. It should be made possible that the user creates and saves its own variant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A second overview is needed, another ABAP will be developed for this requirement. This ABAP will show all the customer data and this list will have the possibility to be printed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;New Query ZZADDRESS_CO&lt;/P&gt;&lt;P&gt;The desired fields of attachment 1 need to be shown in the query.&lt;/P&gt;&lt;P&gt;The selection criteria are shown in attachment 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The column names of the additional data have to changed in the query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer Overview.&lt;/P&gt;&lt;P&gt;Functional specification.&lt;/P&gt;&lt;P&gt;On behalf of this customer overview a standard SAP transaction will be used (transaction VC/2).This transaction will be extended.&lt;/P&gt;&lt;P&gt;The fields are shown on screen with the described headers. Printing of the overview will be done via SAP script. The script makes use of a fixed layout of the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The selection criteria are specified in attachment 2.&lt;/P&gt;&lt;P&gt;The layout of the customer overview and the SAP Script are specified in attachment 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Specification.&lt;/P&gt;&lt;P&gt;The next steps need to be performed.&lt;/P&gt;&lt;P&gt;1.	A routine per infoblock need to be created in Include RV77UNNN. In this routine the data is retrieved and written down to the screen and script,&lt;/P&gt;&lt;P&gt;Example LST1_901 . In include RV77SNNN you can find the standard infoblocks.&lt;/P&gt;&lt;P&gt;2.	Adapt via transaction SE16 table TFRM.&lt;/P&gt;&lt;P&gt;3.	Create a new view in the customizing (sales and distribution- Sales support-sales summary-Assign Reporting Views).Assign the new view to the infoblocks.(Example view 001 is assigned to block 901).&lt;/P&gt;&lt;P&gt;4.	In customizing it is not possible to assign the correct window and element to the infoblock .so this is done via SE16 in table T182A.&lt;/P&gt;&lt;P&gt;5.	Adapt script. Copy script SD-SALES-SUMMARY to a Z-SALES_SUMM.&lt;/P&gt;&lt;P&gt;Assign this new version to the new view in customizing. Create in the main window the element who writes the data on behalf of the print.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Attachment 1 Desired fields&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: Address&lt;/P&gt;&lt;P&gt;~ Customer number                          KNA1-KUNNR&lt;/P&gt;&lt;P&gt;~ Title                                               KAN1-ANRED&lt;/P&gt;&lt;P&gt;~ Name1                                           ADRC-NAME1&lt;/P&gt;&lt;P&gt;~ Name2			         ADRC-NAME2&lt;/P&gt;&lt;P&gt;~ Name3                                           ADRC-NAME3&lt;/P&gt;&lt;P&gt;~ Name4                                           ADRC-NAME4&lt;/P&gt;&lt;P&gt;~ PO Box                                         ADRC-PO_BOX&lt;/P&gt;&lt;P&gt;~ PO Box POSTAL CODE             ADRC-POST_CODE2&lt;/P&gt;&lt;P&gt;~ PO Box city                                  ADRC-PO_BOX_LOC&lt;/P&gt;&lt;P&gt;~ Telephone no1                              ADR2-TEL_NUMBER   1ST RECORD&lt;/P&gt;&lt;P&gt;~ Telephone no2                              ADR2-TEL_NUMBER   2ND RECORD&lt;/P&gt;&lt;P&gt;~ Fax number1                                 ADR3-FAX_NUMBER 1ST RECORD&lt;/P&gt;&lt;P&gt; ~ Fax number2                                ADR3-FAX_NUMBER 2ND RECORD&lt;/P&gt;&lt;P&gt;~ E-mail                                            ADR6-SMTP_ADDR&lt;/P&gt;&lt;P&gt;~ Search item                                   ADRC-SORT1&lt;/P&gt;&lt;P&gt;~ Notes                                            ADRT-REMARK &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: control data &lt;/P&gt;&lt;P&gt;~ VAT registration number              KAN1-STCEG&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: Payment transactions&lt;/P&gt;&lt;P&gt;~Bank country key                         KNBK-BANKS &lt;/P&gt;&lt;P&gt;~Bank key                                      KNBK-BANKL&lt;/P&gt;&lt;P&gt;~Bank Account number                 KNBK-BANKN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: Marketing &lt;/P&gt;&lt;P&gt;~ Industry key                                   KNA1-BRSCH &lt;/P&gt;&lt;P&gt;~ Industry code 1                              KNA1-BRAN1&lt;/P&gt;&lt;P&gt;~ Industry code 2                              KNA1-BRAN2&lt;/P&gt;&lt;P&gt;~ Industry code 3                                KNA1-BRAN3&lt;/P&gt;&lt;P&gt;~ Industry code 4                                KNA1-BRAN4&lt;/P&gt;&lt;P&gt;~ Industry code 5                               KNA1-BRAN5&lt;/P&gt;&lt;P&gt;~Annual sales, currency, year           KNA1-UMSA1, KNA1-UWAER, KNA1-UMAH &lt;/P&gt;&lt;P&gt; ~ Yearly no of employees, year      KAN1-JMZAH, KNA1-JMJAH        &lt;/P&gt;&lt;P&gt;~ Fiscal year variant                          KNA1-PERIV&lt;/P&gt;&lt;P&gt;~Legal status                                      KNA1-GFORM &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: Correspondence &lt;/P&gt;&lt;P&gt;~ Our account number at customer            KNB1-EIKTO&lt;/P&gt;&lt;P&gt; Header: sales &lt;/P&gt;&lt;P&gt;~ Sales office                                              KNVV-VKBUR&lt;/P&gt;&lt;P&gt;~ Customer group                                       KNVV-KDGRP &lt;/P&gt;&lt;P&gt;~ ABC-classification                                  KNVV-KLABC &lt;/P&gt;&lt;P&gt;Header: Invoice&lt;/P&gt;&lt;P&gt;~Tax classification 					KNVI-TAXKD&lt;/P&gt;&lt;P&gt;~Terms of payment key				KNVV-ZTERM&lt;/P&gt;&lt;P&gt;~&lt;/P&gt;&lt;P&gt;Header: Contact Persons&lt;/P&gt;&lt;P&gt;~Title							KNVK-ANRED&lt;/P&gt;&lt;P&gt;~Name							KNVK-NAME1&lt;/P&gt;&lt;P&gt;~Advertising material					KNVK-NMAIL&lt;/P&gt;&lt;P&gt;~Martial Status					KNVK-FAMST&lt;/P&gt;&lt;P&gt;~Notes							KNVK-PARAU&lt;/P&gt;&lt;P&gt;~Function						KNVK-PAFKT&lt;/P&gt;&lt;P&gt;~Department						KNVK-ABTNR&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: Partnerroles&lt;/P&gt;&lt;P&gt;~Personnel Number					KNVP-PERNR&lt;/P&gt;&lt;P&gt;~Name of employee					PA0001-ENAME&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header: Additional Data&lt;/P&gt;&lt;P&gt;~Attribute 1						KNA1-KATR1&lt;/P&gt;&lt;P&gt;~Creation date						KNA1-ERDAT&lt;/P&gt;&lt;P&gt;~Attribute 2						KNA1-KATR2&lt;/P&gt;&lt;P&gt;~Change date of field KNA1-KATR2		CDHDR-UDATE&lt;/P&gt;&lt;P&gt;~Attribute 3						KNA1-KATR3&lt;/P&gt;&lt;P&gt;~Attribute 4						KNA1-KATR4		&lt;/P&gt;&lt;P&gt;~Attribute 5						KNA1-KATR5&lt;/P&gt;&lt;P&gt;~Attribute 6						KNA1-KATR6&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Attachment 2 Selection fields&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;~Customer number&lt;/P&gt;&lt;P&gt;~Sales office&lt;/P&gt;&lt;P&gt;~Personnel Number&lt;/P&gt;&lt;P&gt;~Sales Organization (default NL01)&lt;/P&gt;&lt;P&gt;~Industry key &lt;/P&gt;&lt;P&gt;~Industry codes (1 till 5)&lt;/P&gt;&lt;P&gt;~ABC- classification&lt;/P&gt;&lt;P&gt;~Creation date&lt;/P&gt;&lt;P&gt;~Attribute 1&lt;/P&gt;&lt;P&gt;~Attribute 2&lt;/P&gt;&lt;P&gt;~Attribute 3&lt;/P&gt;&lt;P&gt;~Attribute 4&lt;/P&gt;&lt;P&gt;~Attribute 5&lt;/P&gt;&lt;P&gt;		&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attachment 3 Customer overview + SAP Script&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer master data sheet: 11490                 Page1&lt;/P&gt;&lt;P&gt;Requested by karen Dunnewold		      Date: 25.08.2004&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Address&lt;/P&gt;&lt;P&gt;(Default SAP script ADDRESS statement)&lt;/P&gt;&lt;P&gt;Title&lt;/P&gt;&lt;P&gt;Name1&lt;/P&gt;&lt;P&gt;Street + number&lt;/P&gt;&lt;P&gt;PO Box city&lt;/P&gt;&lt;P&gt;Country&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Search term: ADRC-SORT1&lt;/P&gt;&lt;P&gt;Telephone 1:	 ADR2-TEL_NUMBER	2: ADR2-TEL_NUMBER&lt;/P&gt;&lt;P&gt;Fax 1:		ADR3-FAX_NUMBER	2: ADR3-FAX_NUMBER&lt;/P&gt;&lt;P&gt;E-mail:		ADR6-SMTP_ADDR	&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes: 		ADRT-REMARK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PO BOX&lt;/P&gt;&lt;P&gt;ADRC-PO_BOX&lt;/P&gt;&lt;P&gt;ADRC-POST_CODE2 ADRC-PO_BOX_LOC&lt;/P&gt;&lt;P&gt;T005T-LANDX (T005T-LAND1 = ADRC-COUNTRY)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Control data&lt;/P&gt;&lt;P&gt;VAT registration number:	KNA1-STCEG&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Payment transactions&lt;/P&gt;&lt;P&gt;Country: KNBK-BANKS Bank-key: KNBK u2013 BANKL Bank account: KNBK-BANKN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marketing&lt;/P&gt;&lt;P&gt;Industry 		KNA1-BRSCH	Industry Description&lt;/P&gt;&lt;P&gt;Industry code1		KNA1-BRAN1	Industry Description&lt;/P&gt;&lt;P&gt;Industry code2		KNA1-BRAN2	Industry Description&lt;/P&gt;&lt;P&gt;Industry code3		KNA1-BRAN3	Industry Description&lt;/P&gt;&lt;P&gt;Industry code4		KNA1-BRAN4	Industry Description&lt;/P&gt;&lt;P&gt;Industry code5		KNA1-BRAN5	Industry Description&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Figures&lt;/P&gt;&lt;P&gt;Annual Sales		KNA1-UMSA1, KNA1-UWAER in KNA1-UMAH&lt;/P&gt;&lt;P&gt;Employees		KNA1-JMZAH	                    in KNA1-JMJAH&lt;/P&gt;&lt;P&gt;Legal status  		KNA1-GFORM description&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer master data sheet 11490					Page 2&lt;/P&gt;&lt;P&gt;Requested by karen Dunnewold					Date: 25.08.2004&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Contact Persons&lt;/P&gt;&lt;P&gt;KNVK-ANRED&lt;/P&gt;&lt;P&gt;Mailings: KNVK-NMAIL 		Notes: KNVK-PARAU&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;KNVK-ANRED&lt;/P&gt;&lt;P&gt;Mailings: KNVK-NMAIL 		Notes: KNVK-PARAU&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Correspondence&lt;/P&gt;&lt;P&gt;Our account number at customer 	KNB1-EIKTO&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sales&lt;/P&gt;&lt;P&gt;Sales office		KNVV-VKBUR	Description&lt;/P&gt;&lt;P&gt;Customer group	KNVV-KDGRP	Description&lt;/P&gt;&lt;P&gt;ABC-classify		KNVV-KLABC&lt;/P&gt;&lt;P&gt;Currency		KNVV-WAERS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Invoice&lt;/P&gt;&lt;P&gt;Terms of payment key KNVV-ZTERM 	Tax classification KNV1-TAXKD&lt;/P&gt;&lt;P&gt;						Description	&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Partner (Leave SAP default)&lt;/P&gt;&lt;P&gt;Partnerrole			Number		Name&lt;/P&gt;&lt;P&gt;KNVP-PARVW		KNVP-KUNNR	NAME1&lt;/P&gt;&lt;P&gt;KNVP-PARVW		KNVP-KUNNR	NAME1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Additional data&lt;/P&gt;&lt;P&gt;Attribute1		kna1-katr1	Description&lt;/P&gt;&lt;P&gt;Attribute2		kna1-katr2	Description&lt;/P&gt;&lt;P&gt;Attribute3		kna1-katr3	Description&lt;/P&gt;&lt;P&gt;Attribute4		kna1-katr4	Description&lt;/P&gt;&lt;P&gt;Attribute5		kna1-katr5	Description&lt;/P&gt;&lt;P&gt;Attribute6		kna1-katr6	Description&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2008 06:14:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884382#M933305</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-28T06:14:03Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884383#M933306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi narayana&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;i think u need to write a driving program and a provided with a smatform u sit along with the SD consultant. &lt;/P&gt;&lt;P&gt;ur further views can be shared.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgs,&lt;/P&gt;&lt;P&gt;Venkat.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2008 14:26:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884383#M933306</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-28T14:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP QUERY PROGRAM OUTPUT SHOULD DISPLAY FROM SAP SCRIPT.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884384#M933307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So you want someone to do your work for you?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you don't know what to do go back to your client/team lead/functional consultant and tell them and ask for help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gareth.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 May 2008 14:28:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-query-program-output-should-display-from-sap-script/m-p/3884384#M933307</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-28T14:28:23Z</dc:date>
    </item>
  </channel>
</rss>

