Quantcast
Channel: SCN : All Content - SAP for Utilities
Viewing all 3025 articles
Browse latest View live

Electromobility

$
0
0

Electromobility

 

The number of Electric Vehicles is increasing. The demand for solutions covering the requirements of the EV drivers is growing. The various players in the market, like SAP with the Utilities solution, car manufacturers or mobility service providers need to invest quickly.

 

Here are some interesting postings about Electromobilty:

 

  • Electric Vehicles - The Tipping Point for the Smart Grid by Jörg Ferchow, October 17, 2013
  • Electric Vehicles: Innovation in Motion by Michael Lewis, September 28, 2012 blog
  • Electric Vehicles: They´re Here, Complete With Challenges - and Opportunies / SAP for Utilities Cloud EV Readeness Package  by Moya Watson, September 20, 2012  blog
  • Software for Electromobilty - How SAP Can support the value chain by Jörg Ferchow March 19, 2012 blog

 

 

and the link to the Electromobiltiy Whitepaper "Electric Vehicles: The Tipping Point for the Smart Grid" October 2013 >>www.global.sap.com

 

 

 


AMI related buttons in EC85

$
0
0

Dear Participants and Experts

 

There is a problem that we faced during disconnection on an AMI

When we run EC85 and create disconnection order some of buttons related to AMI installation not shown, can anyone help me, attachment are screen shots and manual screen of AMI.

 

Thanks

EA34 - Screen Exit

$
0
0

Hello Experts,

 

I work for a Utilities project. I need to add 2 more search parameters in the Screen of Tcode EA34 (Mass Processing: Full Reversal ) .

 

I tried searching for Screen Exits but unable to find it.

 

Can anyone help me in fulfilling the above requirement.

 

Thanks in Advance,

Ravi

SAP Multichannel Foundation for Utilities 1.0: What’s under the hood?

$
0
0

Picking up from where Juergen left, in his blog on SAP Utilities  customer engagement strategy, this blog takes a closer look at the central component of the strategy called SAP Multichannel Foundation for Utilities.

 

Motivation

 

Globally, Utilities are striving to shift customer interactions to low cost and high impact digital channels like web and mobile.Most of the Utilities have already and continue to invest in the softwaresolutions like SAP CRM and IS-U to streamline and run their customer centric processes- which are typically used by their employees.The next step is to get their end customers (consumers) access relevant data and processes from the backend business systems and perform the necessary actions on their own, without requiring any human intervention. For example, a consumer gets to know of the upcoming meter read via email, sms or a message that flashes when he/she logs in and then enter the meter reading using a mobile or a web app. The traditional and expensive way would have been to send it via post or calling the call center.

 

The challenge, of course, is how can the Utilities make it happen- without disrupting their well running business systems, make it happen on any channel that the consumer would like to use and making sure the standards of enterprise security, performance and scalability are adhered to. This is exactly what SAP Multichannel Foundation for Utilities or MFU for short, promises to address.

 

In a nutshell

 

 

MFU is essentially two things. First, an out of the box, ready to use multichannel solution with the relevant self-services scenarios pre-configured and pre-integrated with SAP CRM and ISU, bundled with a SAPUI5 template web app . Second a high productivity platform with strong toolset support to allow rapid development of consumer apps that can run on any channel and any device.

 

For the platform part, MFU builds on SAP Netweaver Gateway and the ticket to multichannel is OData. For the yet uninitiated,OData is a non-propriety standardized protocol for providing access to data over internet. OData services can be consumed by any channel that can process XML/JSON received over an HTTP(S) connection- which is pretty much all of the current internet/mobile technologies. Some of the OData consumers:  browsers, excel, adobe flash builder, client libraries – SAP UI5, Javascript, php, JAVA, iphone(Objective C), Windows Phone,Android etc.

 

In simple terms, once the  backend process is exposed as an OData service, it can be consumed in almost any kind of front end app. MFU/NW Gateway provides the toolset that lets easy creation of OData services from  SAP/non-SAP backends and subsequently creation of variety of user  apps out of that. And you do not need any  knowledge of SAP to create these apps, just the typical web/mobile app development skills. In addition to providing the design time, MFU/NW Gateway also provides the runtime/deployment platform for the consumer apps ( acting like a standard app server ).

 

Details

 

MFU_Overview1.jpg

 

 

As shown in the Figure , MFU consists of the following components:

 

  • Utilities OData content and the template SAPUI5web app: Utilities OData entity model derived from Utilities data model from CRM and ISU, along with the default implementation of the OData services to deliver the self-services scenarios. An enhancement framework in addition to what already comes with standard NW Gateway to allow easy enhancement of the Utilities content.  Please note that future releases of MFU  will further add to the content  available for release 1.0 as shown in figure below:

MFU_Process_overview.jpg

 

  • User Management: Central management of online users allowing federation of user identity across different channels. For example: the same user credentials could be used to authenticate users , for example, from a mobile app and a web app. MFU adds to the standard user management functionality provided by NW Gateway

 

  • 360 View: It is essential that in a multichannel customer interaction scenario - irrespective of the channel used by the customer to interact with the Utility, the Utility should have a 360 degree view of the all the user interactions and also the customer should have the single view of the Utility.  This is made possible by implementing a configurable OData service that allows the different online user interactions including the channel information to be logged in the relevant business context as CRM interaction records.  When an agent confirms an account, he/she at once is able to see the past interactions that have happened on mobile or web-for example.  Also it is possible to show the customer his/her past interactions with the Utility giving him the single view of the company

 

  • Channel Analytics: MFU becomes the hub through which all the communication between consumer apps and the backend system is orchestrated. In the process, it collects detailed information on the customer usage of the services.   An OData service allows querying the system for this information which can be subsequently analyzed, for example, with a BW/BI tool to come up with business insights like: Web usage Vs. Mobile Usage, top 5 most used services online, target group of most dedicated mobile app users. These insights can be used by Utilities tofine tune their multichannel customer engagement strategy

 

  • Communication Preference management:   The component captures customer communication preferences (e.g. I want my bill sent by e-mail, outage message by sms ) along with rules ( e.g.  I want the email only on week days) and an engine that evaluates the preferences and the rules in the context of business event (e.g. a billing run, a campaign execution) and then trigger the necessary communication on appropriate channel. Please note that with V1.0, the first piece dealing with capturing of the customer  preferences is delivered, the other pieces will be delivered in the subsequent releases

 

  • Framework components/Tools: e.g. Service builder, UI, consumption tools, security policies etc.- they come standard as part of the NW Gateway

 

Technically, MFU consists of 3 Add-ons, one of each to be deployed on CRM, ISU and NW Gateway. Stay tuned for the upcoming blog that will go in details on the technical pre-requisites and the various deployment options- stuff you need to know to set up and run  MFU in your system landscape.

 

Have a look at other blogs on the same topic.

 

I am looking forward to your comments.

Key Topic: SAP Multichannel Foundation for Utilities

$
0
0

SAP Multichannel Foundation for Utilities 1.0 is available since November 2013 as part of SAP´s Ramp-Up program.


Stay tuned to our blog series to learn more about the solution – what it does, how it works and how you can implement and use it.

 

Read the following blogs regarding the SAP Multichannel Foundation:

 

 

Further blogs are coming soon.

 

Addtional Information:

 

  • To get more information and/or enroll in the ramp-up program, visit http.://service.sap.com/rampup . You can find the SAP Multichannel foundation in the category "SAP Industry-specific Components")

 

 

 

  • To access the Administrator´s guide including configuration details, visit >>SAP Marketplace (choose Industry Solutions - Industry Solution Guides - SAP for Utilities).

Organizational Structure for Work Item derivation

$
0
0

Hi experts,

 

Is the best practice to maintain the organizational structure for work item derivation directly in production or is recomended to treat it as a customzing activity?

 

Thanks!

 

Jing.

Easiest Way to find Exits for any Program

$
0
0

The easiest way to find any exit of t-code is :

 

1. get Program name for the T-code.


2. Goto table MODSAP.

 

2. Pass *<program_name>* in MEMBER field of table MODSAP and execute it.


i.e. For T-code ES32 , Prgram name is SAPLES30.

         Pass *SAPLES30* in MEMBER field of the Table MODSAP.


       Output :

 

SAP Extension Name ( SMOD )TypeEnhancement  (Exits)
EMDI0001EEXIT_SAPLES30_001
EMDI0001EEXIT_SAPLES30_002
EMDI0001EEXIT_SAPLES30_003
EMDI0001EEXIT_SAPLES30_004
EMDI0001EEXIT_SAPLES30_005
EMDI0001EEXIT_SAPLES30_006
EMDI0001EEXIT_SAPLES30_007
EMDI0001EEXIT_SAPLES30_008
EMDI0001EEXIT_SAPLES30_009
EMDI0001EEXIT_SAPLES30_010
EMDI0001EEXIT_SAPLES30_011
EMDI0001SSAPLES300201_CUSTSUB_SAPLXES300100

 

The output is the list of all the exits and Enhancements (SMOD) for that program.

FPMA Run - Error message Posting to General ledger account without tax code not permitted

$
0
0

Hi Friends,

 

With FPMA lauf the following error message has occured "

Posting to general ledger account 496320 D879 without tax code not permitted

Message no. >0014

 

Diagnosis

The G/L account defined in Customizing for cash discount postings only permits postings with tax codes. In this particular case, cash discount was granted for an open item that does not have a tax code. Since there is no tax code for the open item, there is also no tax code for posting the cash discount.

 

System Response

The clearing document is not posted.

 

 

Procedure for System Administration

1. If you want to use the G/L account for postings to which no tax applies, select the indicator posting without tax allowed in the G/L account master record. Goto activity

2. If the system determined the wrong account, change the account determination in Customizing.

Choose Maintain entries.

"

 

But how to find that single item which was posted without a tax code ? In DFKKOP to hit the database where there are million records, is it advisable or any other ideas??

 

Regards and Thanks in advance !

Lakshmi.


EL37 - Deletion of Metering Results

$
0
0

Hello Gang,

 

I have a question about deletion meter reading results.

When we use EL37 the MTR Docs are deleted from the database, which is not what I expect from SAP

After I checked the system I found that there are 2 tables matching to the tables of metering results.

 

EABL -> EABLDEL

EABLG -> EABLGDEL

 

However these tables are not filled.

I am wondering if there is a possibility to move the deleted records to the "DEL" tables instead of deleting them only.

 

Any input is very appreciated.

 

Cheers,

Andreas

Device Change Not Considered in Next Billing Period

$
0
0

Hello Experts,

 

I have the following situation:

 

When there's a device modification (e.g. replacement) one day after a billing period, the removal reading is not taken into consideration in the next billing period.

 

I've searched for some notes, and found out the following:

 

514073 - Incorrect billings with technical changes

The note suggests that periodic readings should occur at the same time of the other readings that might me entered.

 

514963 - Device modification on day after periodic meter reading

The note describes the problem I have but can't be applied

 

I'm studying other alternatives (e.g. Billing Periods for Japanese Market) but would be glad to have information on what was done to solve this issue in other projects.

 

Best Regards,

Leonardo

Duplicate Check by Tax Number

$
0
0

Hi Experts,

 

I have a requirement to check BP duplictaes by Tax number. In other words, any time a BP is being created and has the same Tax Numer as an existing one, the system must not allow the creation of the new BP.

 

I have realized that in these scenarios SAP gives an Info message saying that there is already a BP with this number, but it allows the user to skip the message and still save the BP. Is there anyway to transform this Info message to an error message? Have you had this requirement before?

 

The message code is BUPA_TAX400.

 

Thank you very much in advace,

 

Best Regards,

 

LUCAS

Energy Accounting

$
0
0

Can SAP ISU System provide the following features:

 

1. System should provide a capability to produce energy accounting/energy balance reports at area level and distribution transformer level

 

2. System should have a capability to generate energy profile based on load survey data

 

3.System should provide capability to generate distribution transformer wise energy profile report for different consumer categories for losses analysis

 

4.System should provide capability to relate the consumer indexing information with distribution transformer, feeder, substation, administrative areas

 

5.System should provide validation test for high value customers based of load survey data to analyze discrepancy such as Interval validation, Energy Discrepancy, Spike Interval, Dip Interval and What if analysis for individual customers.

 

With thanks & regards,

Vinodh

Daily Compound Interest calculations

$
0
0

Daily Compound Interest calculations:

 

Guys, if someone is looking for daily compound interest calculations in SAP FICA environment…here you go. SAP AG recently developed and released OSS note based on my requirement…please see the OSS note 1815671.

 

Thank you,

Chinna Katireddy

 

 

1.)  Daily Compound Interest formula for Leap Year:

Amount*(((1+(Interest rate/number of days in a year))^number of days in a month)-1)

For ex:

Principal Amt Due                            : $10,000.00

Annual Interest rate                      : 9% (0.09)

Number of days in a Year            : 366

Interest Calculation period          : Oct 2012

Daily Compound formula              : $10,000*(((1+(0.09/366))^31)-1)

 

2.)  Daily Compound Interest formula for Non-Leap Year:

Amount*(((1+(Interest rate/number of days in a year))^number of days in a month)-1)

For ex:

Principal Amt Due                            : $10,000.00

Annual Interest rate                      : 9% (0.09)

Number of days in a Year            : 365

Interest Calculation period          : Jan 2013

Daily Compound formula              : $10,000*(((1+(0.09/365))^31)-1)

Research on Smart Water Management: First Prototype Available

$
0
0

One of the most significant barriers to promoting efficient water-energy use in water distribution systems is insufficient supply of data about water and related energy consumption in the network and at consumer sites. This poses a challenge to policy-makers and regulators when trying to determine appropriate measures to promote efficiency for either context and to help consumers understanding and improving their water consumption habits. Smart meter technologies grant access to real-time data and to the history of water usage by consumers and utilities. This data allows for identification of when and how much water was respectively is being consumed, as well as opportunities for efficiency improvements, namely efficient water use in the household and utility-level control of water losses and cost-benefit water planning.

These challenges are currently under research in the context of the EU-funded research project iWIDGET (http://www.i-widget.eu/). As the first year of this three years project has already passed, this blog post intends to give a short summary and insight to preliminary results including the selection of use cases, which are of prime interest for water utilities.

 

The EU-funded project iWIDGET

 

The aim of the EU-funded iWIDGET (Improved Water efficiency through ICT technologies for integrated supply-Demand side manaGEmenT) project is to advance knowledge and understanding of smart metering technologies in order to develop novel, robust, practical and cost-effective methodologies and tools to manage urban water demand in households across Europe, by reducing wastage, improving utility understanding of end-user demand and reducing customer water and energy costs. The main scientific challenges for iWIDGET are the management and extraction of useful information from vast amounts of high-resolution consumption data, the development of customised intervention and awareness campaigns to influence behavioural change, and the integration of iWIDGET concepts into a set of decision-support tools for water utilities and consumers, applicable in differing local conditions.

In order to meet these aims and challenges, iWIDGET will investigate: (1) how best to provide the dynamic accurate measurement and data transfer of useful information about end-user water consumption, (2) how best to use consumption data to improve the operation of utilities and influence end-users to modify their behaviour, (3) how to arrive at the best business model to convert a promising technology into a useful and cost-effective product, and (4) how to demonstrate and validate the new methodologies on two case studies in the North and South of Europe.

The project consortium consists of partners from all over Europe, and combines Universities, industrial partners and pilot companies (water utilities):

  • University of Exeter, UK
  • HR Wallingford LTD, UK
  • IBM Ireland
  • Laboratorio Nacional de Engenharia Civil, PT
  • Nacional Technical University of Athens, GR
  • SAP (Switzerland) AG, CH
  • Utility Partnership LTD, UK
  • AGS- ADMINISTRACAO E GESTAO DE SISTEMAS DE SALUBRIDADE AS, PT
  • Waterwise Project LTD, UK
  • Southern Water, UK

 

iWIDGET Use Cases

 

A major activity in the first year of the project was the development of interesting and appropriate use cases, which should cover a broad scope of applications that build upon exploitation of data related to water and energy usage in water distribution systems and consumer households. These use cases are considered important current challenges of water utilities and are intended to serve as basis for the development of solutions by the project partners.

In order to obtain a comprehensive list of possible use cases, the following methodology was used. First, a list of high-level use cases was compiled, described and harmonized. High-level use cases were used to describe the main process in iWIDGET system and were aligned with the project objectives. For each high-level use case, a list of detailed-level use cases was subsequently compiled, described and harmonized. Detailed-level use cases exhaustively describe the sub-processes within a given high-level case. At a second stage, the proposed high-level use cases were validated and prioritized, based on the contributions of two different target audiences - the project partners and dedicated stakeholders. In step three, the use cases were revised for relevance to the project and technical feasibility.

In the following the resulting high level use cases are briefly described. Two domains are differentiated for the uses cases, the consumer domain and the water utility domain (Use cases and descriptions are adapted from the project document iWIDGET Task 1.2 Use Case Description).

 

Consumer Domain:

  • Use Case C1: Obtain water consumption data: This use case is devoted to the detailed monitoring of water consumption at the household level, using real-time data from smart meters. The iWIDGET system enables householders to follow the progress of their total and per appliance water consumption in real-time basis, through an advanced visual environment that incorporates many graphical abilities and features.
  • Use Case C2: Understand water consumption: This use case comprises all facilities of the iWIDGET system, which enable householders to monitor and understand better the water consumption profile of their household. The system uses real-time as well as historical consumption data in order to execute and display useful comparisons. Through an advanced visual environment, the users can compare the current water consumption of their household with other neighbouring consumers, with consumers of similar characteristics, with more efficient households or with the historical consumption data of their household. This process aims to motivate users to change their wasteful behaviours. Additionally, the system assists householders to improve water efficiency of their house, by identifying the wasteful and inefficient water uses and appliances. Finally, the iWIDGET system has the ability to detect on real-time basis various faults related to water, such as bursts and leakages. The long-term water consumption trends of the household are also monitored for the detection of abnormal situations which could be linked with other factors, such as health.
  • Use Case C3: Get assistance to increase water use efficiency: This use case addresses more efficient use of domestic water. The iWIDGET system can assist and motivate householders to decrease their water and energy consumption, through customised and alternative suggestions which include practices, tips and interventions. Apart from general water-saving tips, the system, based on the specific needs and characteristics of the household, can compose and perform different hypothetical but realistic scenarios, using various combinations of innovative technologies, such as water-efficient appliances, rainwater harvesting systems, greywater treatment systems, advanced gardening systems etc. For each proposed practice the system presents the profit and the cost of the implementation. One other basic function of iWIDGET is the forecasting of consumers’ next water bill
  • Use Case C4: Control water use: This use case comprises some advanced functions of the iWIDGET system that assist the users to schedule the various water uses of their household, in an optimal way. The user can choose the appliances that are going to operate during the day and the system uses customised scenarios to try to schedule these appliances in a way that water/energy bills will be optimised. Moreover, the iWIDGET system can communicate remotely with smart appliances in order to control them based on the already conducted schedule. The system can also operate as a means to control the advanced water saving technologies (water harvesting systems, greywater treatment systems).

Water Utility Domain:

  • Use Case W1: Obtain water consumption and related energy consumption data: The water utility has access to near real-time data about metered water and associated energy consumption. Water consumption data comes from SCADA, smart metering and includes network inflow, total metered consumption and total metered consumption per category of consumer. Associated energy consumption data comes from SCADA and is related to network pumping if it is present in the system.
  • Use Case W2: Understand water consumption: The water utility receives near real-time information on the different components of metered water consumption and water losses (real losses, apparent losses, unmetered consumption).
  • Use Case W3: Get support to increasing operational efficiency: The water utility receives real-time information on the effects of pressure control on consumption components, adaptive pumping scheduling regarding energy costs and consumption profiles and optimal placement of valves and flow meters on pipes in the network.
  • Use case W4: Get support to increasing the quality of service: The water utility receives information on billing, complaints and potential residential leakage.
  • Use Case W5: Get support to improve consumer efficient water use: The water utility receives customized suggestions on adaptive pricing schemes and awareness campaigns.
  • Use Case W6: Get support for system planning and design: The water utility receives information on reliable demand forecasts considering context factors (e.g., socio-demographic, tariffs) to support decisions on network expansions and on optimal replacement period of equipments.

 

First Prototype

 

After the use cases had been developed the implementation of the iWIDGET system architecture and first prototypes commenced. In general the overall iWIDGET architecture (cf. Figure below) was divided into several components that are loosely coupled to be developed by partners independently.

arch.png

An important component is the iWIDGET central database, which provides smart meter data through a REST web service API. This data is accessed by several components also called widgets that implement the different use cases. In the context of the project SAP is responsible for use cases W1 and W2. In a first prototype the use case W1, i.e. obtain water consumption and related energy consumption data, was implemented. In this use case important consumption statistics are calculated to support a first understanding about flow and consumption data. Teh following two figures are screenshots of the developed prototype running in portlet mode. It features a two level hierarchy for navigating the different functionalities and use cases. The tabs on top represent main functionalities, which if necessary contain a secondary hierarchy at the bottom. For example the Consumption Overview tab has three different available analytic functionalities: Meter overview, DMA inflow/consumption and consumption categories. On the left hand side available filters are displayed and in the center two charts are displaying requested data. The chart on top shows totals whereas the lower chart visualizes these totals over time.

screen1.jpg

In the figure above, the meter overview analyses are presented. Here the utility staff can select a set of utility meters for analysis over time. In the data set outflow and inflow meters to DMAs are distinguished. The figure below depicts a screenshot of the DMA inflow versus consumption analyses. Inflow to DMAs can be directly compared to the consumption caused by connected residential and commercial consumers.

screen2.jpg

Technically, the prototype was implemented using only open source software available via free licences, e.g. Apache Licence, Version 2.0. In more detail the Vaadin framework (https://vaadin.com/) and the Dojo Toolkit (http://dojotoolkit.org/) were used.

 

 

For further information please contact Christine Grimm (Project Lead, iWidget)

Disclaimer: This blog post is mainly based on the document iWIDGET Task 1.2 Use Case Description.

Invoice in FICA for charges

$
0
0


Hi,

My customer want to process invoice from FICA for charges - dunning charges and other charges that he post via FPE1.

Can I use the invoice process from FICA for that ?

Do I need also to create a billing document before ?

From what I understand the process is Billing doc- invoices doc and then posting the docuement.

Is it possible to collect to the invoice a document that was already being post via FPE1 without creating a billing document ?

thanks,

Vered


Activate FI-CA without activating any IS solution

$
0
0

Hi Experts,

 

Is it possible to have all functionality of FI-CA in ECC without activating any IS solution. I was just doing a comparison and I have following observation:

  1. Billing & Invoicing Transactions were missing in Easy Access menu in ECC FI-CA.
  2. Dunning by Collection strategy node was missing in SPRO menu in ECC FICA.

 

My Question would be, can anyone tell me the

  1. Major difference between ECC FICA and IS FICA.
  2. Can ECC FICA be used for the same purpose we use in IS solution.
  3. Does Extended FICA (FICAX) have all functionality of IS- FICA like for e.g. RMCA & PSCD.

 

Thanks & Regards

Satyajeet

Dunning reversal & installment plan

$
0
0

Hi Experts,

 

Installment plan gets deactivated after the dunning run.

 

When I reverse the dunning run with FPVC , can I possibly re-activate the installment plan ?

 

Please let me know if there are any other ways to reactivate installment plan..which was deactivated due to dunning.

Like config..etc

Thanks in advance for your help!!

 

Regards,

Nachiket

FQ EVENT 0020

$
0
0


Hi Floks,

 

I need help on how to handle the cancel disconnection documents when ever recevies payment file. Currently I am using the FQ event 0020. Here when payments are recevied  the logic is setup such that dis.connection documents will get completed by trigerring workflows.

 

The issue I am facing is the performance issue( its consuming lots of resources).

 

Please suggestion me the best approach to handle the current scenario.

 

 

Thanks

KRG.

Key Topic: SAP Multichannel Foundation for Utilities

$
0
0

SAP Multichannel Foundation for Utilities 1.0 is available since November 2013 as part of SAP´s Ramp-Up program.


Stay tuned to our blog series to learn more about the solution – what it does, how it works and how you can implement and use it.

 

Read the following blogs regarding the SAP Multichannel Foundation:

 

 


Further blogs are coming soon.

 

Addtional Information:

 

  • To get more information and/or enroll in the ramp-up program, visit http.://service.sap.com/rampup . You can find the SAP Multichannel foundation in the category "SAP Industry-specific Components")

 

 

 

  • To access the Administrator´s guide including configuration details, visit >>SAP Marketplace (choose Industry Solutions - Industry Solution Guides - SAP for Utilities).

Create Debit doc while payment posting using FP05

$
0
0

Hi Experts,

 

I have an urgent requirement to be solved in FICA, as i am new to this.

I have the requirement to post the Debit Document say of Document type XX on the account, while payment is being posted using FP05.

 

I have already tried with the FM - FKK_CREATE_DOC in the event 0010 and 0020, but whenever i am trying to post, it just post the Document for the Payments only, i am nt able to post the Debit doc (something is going wrong).

 

** One more point to mention, i checked FM - FKK_CREATE_DOC_ADDITIONAL, and what i understood is that we can generate the additional documents, but will it create the Document with different Document type with different Main/Sub, or the same as the one as FP05. Because  i want to post debit document of different Doc type XX with main/sub.

 

Please help me out with this (and it would be helpful if u help me out with what all parameters to be passed as well).

 

Thanks & regards,

RJ.

Viewing all 3025 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>