Hi All,

Kindly let me know about the 'content admin' access.

where can we find this ?

what does it mean exactly?

what's the use of this after BO report development?

Please help me over this.

Thanks

Ram

hi,

     After i create a dashboard using sap design studio 1.6 for mobile , on some mobile device the view is normal as its need to be but on other mobile  devices  is not properly viewing..

          :-on phones that have 540x930 and greater resolution it workes fine

                                          480x850 and less resolution the components are not properly mapped .

     is their anything i can do about it? need help..

Hi All,

This discussion is regarding twitter integration with SAP CRM for which I followed the snote :1832480 "How to implement Twitter API for CRM Interaction Center". After doing all the steps still not able to integrate with SAP CRM.

Below are the doubts/problems that I have regarding twitter integration.

     1) Is there any background job program by which data's are fetched from twitter based on tokens?

     2) How will the implemented class methods are executed as we are not specifying which method to execute based on button click or event?

     3) When I  execute my implemented class 'get_post' method its giving the below error. Could anyone suggest the cause of this issue?

Note : I have imported SSL for twitter using STRUST.

Thanks in Advance.

Regards,

Bob.

In this blog , i would like to share my experience attending the CodeJam @SAPLabs Bangalore held on June 16th by RIG Team (Yes,this is the same team who rapidly innovates with different SAP Mobile and Cloud Products and publishes great content in SCN)

The event was scheduled from 10 am to 5 pm with complete hands on exercises for developing applications on HCP.

I always wonder how SAP remains to be the leader and dominate the Enterprise market innovating with the products on Cloud,In Memory,Mobile, IOT solving the crucial business problems of its customer with technology !!!

(The entrance pic at SAP Labs Bangalore was taken from a tweet by @LifeatSAP)

Checking in at Labs gave me the answer.

It is just because of the strategic leadership and they inspiring their teams to produce great work every moment during the day. Right from the moment they step into the campus.

Just look at the above picture at the entrance of SAP Labs.Why would n't one inspire to deliver the best out of him every day. No wonder for SAP Labs being one of the best workplaces to work for.

Once the participants are in their places Vasu Kesiraju along with Midhun VP and Babu Ganesh Vkicked off the session by introducing themselves and the new budding baby of SAP - 'HCP'. They discussed its strategy ,newly introduced services, different integration scenarios with other cloud solutions acquired by SAP.and much more. Over the course of period, participants started working on the exercises where the RIG Team geeks pitched in at participants when ever needed.

(Architecture of HCP services and its integration points of Hadoop and Vora communicating with on premise systems explained by RIG team to #RunSimple)

The exercises are tailored to introduce the Platform and quickly develop applications using its services. It comprises of consuming an external API in HTML 5 app, Developing a secure Java app and deploying to HCP, Developing the Persistency with JPA and exposing it as OData service , Consume OData service in UI5 app via WEBIDE.

This is a good enough content to develop more end to end apps in HCP once completing the exercises .Instructors also made sure that all participants get the most of the session and executed them successfully.

Participants also shared their IOT and HCP project experience and contributed to make the event align with real world requirements.

(Participant explaining his project on IOT and Vasu, Midhun helping participants executing the exercises)

(There was an error while executing one of the exercises and the traditional Geek Diet made it to work.)

( These Geeks have already learned developing apps using various HCP services and ready to do more. Have you? )

Attending this event helped the participants to learn more on HCP, its future strategy,its integration with other SAP acquired Cloud solutions and inspired me to do more good work with SAP products and help our customers.

Thanks to RIG folks Babu Ganesh V , Midhun VP and Vasu Kesiraju and the team behind them for organizing another great event and pushing new technologies into customers.

The exercises of this CodeJam are available here.

Follow the space SAP CodeJam and keep looking at the Upcoming Events section to attend any event near you. Don't miss them. It really helps.

Have n't found any events near your location? Look at this blog post to host a CodeJam for free in your location.

Introduction

In this series of documents, I will introduce you to the concepts and ideas that sit behind SAP's API Management offering.  We'll start by looking at the "the big picture", and then as we progress through the documents, we'll dive deeper into the details so you can see how all the pieces fit together.

By the end of this series of documents, you will be able to build a real-life API Proxy that exposes a Web Service from a backend system.

So, let's start with the 30,000 feet overview...

Where We've Come From

It has long been known that lots of powerful business functionality lies buried deep inside every SAP system.  However, the challenge has always been how to get at that functionality in a consistent and easy-to-consume manner?

Back in the mid-nineties, the Remote Function Call (RFC) interface arrived on the scene (1994 if my memory serves me correctly).  Originally, the RFC interface was accessed from outside the SAP system via a set of C libraries that allowed an external C program to call any ABAP function module that had the "Remote Enabled" flag switched on.

This was certainly a good start, but it was fairly restricted in its adoption for the simple reason that first, in order to make use of this interface you had to be a C programmer, and second, you had to have some internal knowledge of the SAP system in order to understand the data being sent and received.  Needless to say, adoption was limited.

Then, the libraries for accessing the RFC interface were expanded to include Visual Basic and this new fangled language from Sun Microsystems called "Java".  For a while, it looked like everyone was happy.  Visual Basic and its MS Office counterpart "VB for Applications" was widely used and Java was growing in popularity.  But the whole use of RFC based access to SAP imposed a barrier to adoption.  RFC was a proprietary protocol and required the external developer to have at least some knowledge of how an ABAP function modules works.

But the mid-nineties saw the invention of another technology that has now totally transformed the face of both the retail and business computing world - the World Wide Web (now often referred to by non-technical people as "The Interwebs").  Quite soon, businesses began to see the benefits of giving customers access to their systems through these new bits of (not very compatible) software called browsers.

But as with any emerging technology, there's always a scramble for market domination and whoever wins this scrap tends to be able to set the technical standards for how that software should behave.

All of these changes provided SAP with a significant challenge because at that time, the ABAP kernel had no way to communicate using any protocol other than DIAG (used by SAPGUI) and CPIC (used for Remote Function Calls).  Back then, this new fangled protocol called HTTP was completely incompatible with ABAP systems.

So to get the ball rolling, SAP implemented a protocol translation layer called the Internet Transaction Server.  The main job of this software was to translate HTTP messages arriving from browsers into either the DIAG protocol used by SAPGUI or the RFC protocol, then to translate the outbound response from the SAP system back into HTML for the browser.

Shortly after the ITS was released, and In parallel to its development, a project started to allow an ABAP kernel to send and receive XML based messages using the HTTP protocol.  This then became the foundation of what is now the Internet Connectivity Framework

Step forward now to the Millenium Year and a researcher at the University of California, Irvine by the name of Roy Fielding was granted a doctorate for his thesis called Architectural Styles and the Design of Network-based Software Architectures (available here https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm if you're curious).  From this paper, the widely popular concept of Representational State Transfer, or REST has been acquired.

The architectural principles of REST are now taken to be the de facto design philosophy behind all well designed Web software.  Unfortunately, the term "RESTful service" has been bandied around so much nowadays, that some people talk of REST as if it is an alternative protocol to HTTP.  "Yes, we have two types of service, HTTP and REST".

Which reminds me of a scene from the Blues Brothers: Classic Movie Line #5 - YouTube

But anyway, I digress...

All through the browser wars of the late nineties and early naughties, people were experimenting with different protocols.  During this time, SOAP based Web Services started to become widely used (in spite of their dubious grasp of the principles of REST)

All this to say that everyone knew that backend business systems contained lots of useful information and functionality - its just that nobody could agree on a single, unified protocol through which these backend systems could be accessed.

And even today, people still can't agree...

Leveling The Playing Field

In all of this technical maelstrom of conflicting or ambiguous interface standards, and with the petty squabbles over my-interface-is-better-than-your-interface, various companies have decided to sidestep the whole issue and provide software from which anyone can that create their own standardisation layer.  One such company was Apigee.

What SAP has done is to implement the Apigee Edge software as a cloud-based service and then provide all HCP users with access to it via a service called "SAP API Management".

Using the functionality of API Management, you can develop your own proxies to almost any backend service you like - and there's no restriction here to access only SAP backend systems.  You can access any system that is visible to the public internet and supports HTTP based communication.

APIs Are The Fuel That Drives Innovation

Any backend business system (such as an SAP ERP system) is known as a "System of Record".  These systems need to be rock-solid stable simply because large businesses are entirely dependent on the data contained within, and the functionality provided by these systems - if such a system goes down, its quite possible that part (or even all) of the business stops working!

Consequently, these systems do not change either very often or very quickly.

However, in the brave new world of Agile software development and the accelerating pace of change, the systems with which the end users interact are expected to stay up to date with the latest technological developments.  This means new layers of software must be built on top of the systems of record that can accommodate the expectation for a more rapid pace of change.

Hence we now see the emergence of Systems of Engagement that sit on top of the Systems of Record.  Systems of Engagement change faster than the underlying Systems of Record, but still not fast enough to keep up with the pace of change that occurs with technology innovation.  Therefore, we see a third layer of software known as Systems of Innovation.

Systems of Innovation are where the latest technological advances are implemented - yet at the same time, these apps need to access the same functionality exposed by the backend systems of records.

Therefore, to provide a standardised interface, SAP API Management sits in between the systems of Engagement and the Systems of Innovation.

Enabling Innovation and Bimodal IT

In the world of API Management, the term "Bimodal IT" refers to the practice of managing two separate, yet coherent modes of IT delivery: one focused on stability and the other on agility.

Mode 1 is traditional and sequential, emphasizing safety and accuracy.

Mode 2 is exploratory and nonlinear, emphasizing agility and speed.

Starting Your API Management Service

To gain access to this API Management service, you must at least have a Trial Account on the SAP HANA Cloud Platform.  If you don't have one of these, please go and set one up now...

From your HCP account, from the menu on the left, select Services, then scroll down to the section titled "Integration" and click on the "SAP API Management" tile.

When the API Management service screen appears, you will see that there are several different links you could select:

1. The API Portal.  This is used by a proxy developer for creating API Proxies and Products
2. The Dev Portal.  This is used by the developer of a frontend application when they wish to consume an API Proxy developed by the proxy developer
3. Service Configuration.  Here there are two further links that allow you to configure the roles and destinations used by API Management

Click on the link to access the API Portal (not the Dev Portal!) and you will see a screen similar to the following.  If this is the first time you've accessed your API Management tool, then all the counters on these analytic tiles will be zero.

Before we dive into the details of how to build an API Proxy, it is very important that we first understand two things:

1. The data objects with which we will be working
2. How these data objects are related to each other

Overview of API Management Data Objects

In API Management, you will be working with 4 different data objects.

Systems

The first type of data object is a "System".  A system is simply a logical name for some backend system of record.  Each system you define will act as the provider of backend functionality such as Web Services or OData Services.

API Proxies

An API Proxy is the data object that contains all the functionality to be executed when an external user wants to access the backend service.  Within the API Proxy you can implement all manner of functionality such as checking that the user has not called this API more times that are permitted by their quota, or preventing a denial of service attack with a tool known as a "Spike Arrest", or translating the incoming request into a SOAP XML payload, or performing your own custom written functionality, etc etc etc...

To be honest, the development of an API Proxy is where 99% of your development effort will go.  You can think of the API Proxy as the heart of API Management.

Each API Proxy represents the interface to a single backend service,  You cannot create an API Proxy that is a mashup of data received from different backend services.  If you want to do that, then you should look at HCP's OData Provisioning service and not here in API Management - this is the wrong tool for that particular job.

Products

Now this is where the fun starts (as if we aren't having fun already...)

It is not possible for an external user to consume an API Proxy directly.  In order for your API Proxy to be visible to the outside world, you must first add it to a data object known as a "Product".  The purpose of a Product is to group proxies together into units that represent all the services needed to perform some larger unit of business functionality.

You should think of a Product as The unit of API exposure

The important thing to understand here is that in addition to an Product being able to contain multiple API Proxies, one API Proxy can be added to multiple Products.  This results in the formation of something called a many-to-many hierarchy, like this:

So remember: one API Proxy can be added to multiple Products, and one Product can contain multiple API Proxies.

Either way, if you do not add an API Proxy to a Product, then no external user will be able to consume that API Proxy - it will remain completely hidden from view.

Applications

Finally, we come to the last data object known as an Application.

We must be very careful to understand what is meant here by the use of the term "application", because in the context of API management, the term "application" does not carry the conventional meaning.

The conventional meaning for the term "application" is a unit of software with which a user interacts in order to perform some business task.

In the context of API Management, an "application" is the unit of API consumption.  In other words, if you, as the developer of some external business application wish to consume the API Proxies exposed through the various Products, you must declare your usage of those Products by the creation of this data object known as an "application".

In other words, in API Management, an "application" represents one user's subscription to a specific set of Products.  If a different user wishes to subscribe to the same set of Products, then they must create their own application.  This is how API Management is then able to manage the usage of APIs and keep track of things like quotas.

As we've already seen with API Proxies and Products, there is a many-to-many relationship between Products and Applications.  One Application can contain multiple Products, and one Product can be consumed through multiple Applications.

Two Different Perspectives: Development and Consumption

As was described above, there are two different tools used for the development and consumption of API Proxies.

If you are the developer of an API Proxy, then you use the API Portal and are concerned with creating the data objects outlined below.

However, if you are the developer of some front end application such as an iPad app, then you will be looking at the API Proxies from the perspective of a consumer, not a developer; therefore, you will use the Dev Portal and be concerned with the data objects outlined below.

In the next document, we will look in overview at the development of each of these data objects: Systems, API Proxies, Products and Applications

Chris W

Release of SAP S/4HANA, on-premise edition 1511

In November 2015 (1511) updates have been released for both, SAP S/4HANA, on-premise and cloud edition. In November 2015, SAP delivered a massive wave of simplification and innovation in the core of SAP S/4HANA. With this delivery, enterprises can drive unprecedented business value with innovative use-cases - in core financial and operational areas such as in logistics – taking full advantage of a simplified data model and a responsive user experience.

Key simplifications and innovations include:

• Optimized working capital with new accounts payables and receivables cockpits
• Decreased stock buffers with simplified data model in inventory management for real-time, high-volume processing
• Increased visibility with real-time stock and material flow insight
• Reduced manufacturing cycle time with streamlined material flow for internal requirements (MRP)
• Augmented reactivity with real-time monitoring of production orders regarding flow and critical issues
• Improved operational decisions with easy simulation of supply alternatives
• Lower procurement costs with standard integration to the Ariba Business Network
• Better customer service with new sales order fulfillment cockpit for instantly identifying bottlenecks and issues

For more information see as well the SCN blog from Sven Denecken: Link

The System Conversion to SAP S/4HANA, on-premise edition 1511

Different transition paths are supported with SAP S/4HANA, on-premise edition 1511:

• New Implementation
  New installation of SAP S/4HANA e.g. for customers migrating a legacy system.
• System Conversion
  Customers who want to change their current system into a SAP S/4HANA system.
• Landscape Transformation
  Customers who want to consolidate their landscape or to selectively transform data into a SAP S/4HANA system.

The SAP S/4HANA, on-premise edition 1511 system conversion supports one-step procedure (Database, SAP NetWeaver and application transition in one step) for SAP ERP 6.0 EHP x…7 systems. System Conversion requires a Unicode (UC) source system. Non-Unicode source systems will require a two-step approach (first move to Unicode then to SAP S/4HANA, on-premise edition 1511).

Basically it can be distinguished between technical and semantic tasks during the system conversion. The technical installation procedure is based on established lifecycle management tools (Maintenance Planner, Software Update Manager [SUM] and Database Migration Option [DMO]). Due to the fact that SAP S/4HANA is a new product line (and not the successor of SAP Business Suite) things are done differently in SAP S/4HANA.

• Many of the changes are technical in nature and have no or only limited impact on peoples work and thus do not trigger business change management. Such changes will be mandatory when converting a system to SAP S/4HANA.
• Other decisions are more of a strategic nature determining which version of functional support will evolve into the digital era and provide the capabilities demanded from the unstoppable business process innovation. Where those strategic directions demand change management through adoption, SAP at large keeps the traditional capabilities available as compatibility scope enabling a rather technical migration of these processes and leaving the time of change management at customer decision that may well happen when initially converting or at a later point in time.

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

The technical procedure – well established tooling

Maintenance Planner

The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the conversion.

The Maintenance Planner is a pre-requisite for the system conversion to SAP S/4HANA, on-premise edition 1511. The Maintenance Optimizer (MOPZ) is not used

For more information regarding Maintenance Planner see SAP Help: http://help.sap.com/maintenanceplanner

Software Update Manager (SUM)

Software Update Manager (SUM) is the technical tool for system conversion to SAP S/4HANA, on-premise edition 1511.

Note:

• You must run the Maintenance Planner before the SUM.
• Ensure that the latest version of the Software Update Manager is used:

For all information about using the SUM, please see the document Conversion of SAP Systems to SAP S/4HANA, on-premise edition Using Software Update Manager available at:

• service.sap.com/sltoolset (LINK)
  • Software Logistics Toolset 1.0
  • Section "Documentation"
  • System Maintenance

Database Migration Option (DMO)

DMO - the one-step-migration to SAP HANA database for SAP systems. It is called "database migration option (DMO) of Software Update Manager (SUM)". For SAP S/4HANA it combines the installation of the SAP S/4HANA, on-premise software and database migration to SAP HANA in one tool

See the following SCN Blog with helpful information regarding DMO - SCN LINK

Adoption Tasks – how SAP support the customer

Simplification List for SAP S/4HANA, on-premise edition 1511

To allow our customers a better planning and estimation of their way to SAP S/4HANA, we have created the “Simplification List for SAP S/4HANA, on-premise edition 1511”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and solution capabilities. In some cases, we have merged certain functionality with other elements or reflected it within a new solution / architecture compared to the SAP Business Suite products.

For more information see Simplification List for SAP S/4HANA, on-premise edition 1511 (FPS1): PDF

Conversion Pre-Checks

Pre-checks are shipped as SAP Notes to customers that want to convert to SAP S/4HANA. Customers can use these pre-checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the instances that need addressing before attempting the conversion process. The checks are run twice again during the conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist.

Implement SAP Note 2182725, and all the related notes attached to it. Make sure to use latest version of this note and regularly check for updates of all attached notes. Implement and run these reports on every system (Sandbox, DEV, QA, PROD) you want to convert to SAP S/4HANA, on-premise edition 1511. Report R_S4_PRE_TRANSITION_CHECKS.

Custom Code Checks

These checks are based on the Simplification list concept. Before converting to SAP S/4HANA, on-premise edition 1511 you need to check your custom code against the SAP S/4HANA simplifications. These simplifications are loaded into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not comply with the scope and data structure of SAP S/4HANA 1511, on-premise edition

For more information about the Custom Code Check tool, see SAP Help Portal: Link and the following SCN blog: SAP S/4HANA Custom Code Migration Worklist.

Related information – at a glance

Hello,

In a sales order header text tab for some text id's like job name and subject are coming in English and logon langauge is 'DE'.

In Access Sequences it maintained for all langauges. Kindly suggest.

Earlier response would be appriciated.

Thanks.

Dear All, we are planning to implement the reason code to our client but we have some doubt to be clear please help us we  have tested some scenario in our DEV system our doubt is as below example customer has paid excess payment invoice value is 400 Rs and Payment received to the bank is 500 now in our books through F-28 accounting entry will follow as below Customer Cr 400 Reason code a/c Cr  100 Bank a/c              Dr  500 but  doubt is if the excess payment happen customer should be credit of Rs 100 should show in the open item of the customer if we implement reason code then it will create mess please advice

Hi expert.

I have confusion in the Product costing month end activity.

I need to know the flow of the ME.

The list is below , But i dont know which one should be executed first ..

cost estimate

WIP calculation

Variance calculation

settlement .

Kindly let me know the step by step month end activity.

Thanks

Dear All,

We need to set up the  Accrual Difference Procedure for Money Market & Bonds, when i go through the config i found the below update types kindly advise which set i can consider for MM & which set for Bonds.

AD1004 - Accruals - Difference Procedure: Revenue

AD1005 - Accruals - Difference Procedure: Expenses

AD1014 - Deferrals - Difference Procedure: Revenue

AD1015 - Deferrals - Difference Procedure: Expenses

I am unable to figure out what is the difference between  AD1004 & AD1014 , AD1005  & AD1015  both has the same description, what is the difference between these, Kindly provide me some guidance on the same.

Regards,

Reenu John

hi SD experts,

if i want to create the new sales document types (VOV8) but the probability field was disable mode how can i enter the 100% in that field is there any assignment for that if at all if i go for standard one (OR) there was a 100% of probability how can i achieve this could you please share your valuable ideas on this

regards,

rayudu

Hi pros,

How can I access the data from another solution? Example: I created a solution A with extension field for a Lead, then a create a solution B for an Opportunity. How can I use extension fields created in solution A inside the solution B?

Best regards,

Nadezhda Rukavishnikova

Greetings

We are implementing S4HANA, and we are customizing revenue accounting 1.1; We have already done Revenue contracts and POBs, but all of them have had "transaction price" in Zero; the condition type that we are using is “PR00” (Customizing “Define Condition Types for Standalone Selling Price and …”) and in the transaction VK11 we have created stand-alone prices for this, but I still having the issue.

We have created the 3 application that the help configuration says in BRF+, also we have filled the decision table "DT_PROCESS_POB" and the POB Type, with the field "Excl. from Alloc." with value "X" because we need that the invoice price and the contract price will be the same. There is not much information about how create rules in BRF+, but at this time, only at the price determination we have had problems; We need resolve this issue for follow with the account determination and review the posting.

Your help for know what we are missing for get the price of the invoice in the contract price or transaction Price.

Any thoughts people ...

i) Tried to export Flavors, Themes & Resources .... my export file doesn't seem to include the Theme information?

ii) Importing what is in the file my flavors go into my gallery and have to be manually re-assigned to the t-codes ... is that the way it's supposed to work?

iii) I'm getting this message for my SMEN flavor 'Backend Error Occured'

A running Personas script could have caused this error. Please check your active scripts.

Received "control serialization failed" on batch step: {"get":"state/ur"}

The complete batch was:
[{"get":"state/ur"}]

OR

A running Personas script could have caused this error. Please check your active scripts.

Received "control serialization failed" on batch step: {"get":"state/ur"}

The complete batch was:
[{"post":"action/3/wnd[0]/usr/btnSTARTBUTTON"},{"get":"state/ur"}]

depending on how I go at it.

Regards.

Patrick.

Hi Team ,

Environment : BI 4.1 SP6

Lumira on BIP :1.29.3

Can Lumira connects to Sharepoint as a datasource ?

Our requirement is to create .lums on Excel files stored in Sharepoint .We've gone through thread Lumira connectivity to Sharepoint?

It says we can connect to Lists with Generic ODATA 2.0 driver ,which is out of box connectivity . I think Excel files also stores under Lists .

Did anybody worked on this ? How do we do this ?

all the features includes schedule and refresh works when published to BIP ?

Do we need any third party drivers to refresh them in BIP?

Thank you.

Is it possible to replicate Employee Data using Data Services?

If so, does that Data Services Job use a web service or an IDOC to populate the following:

Org Structure

Employee Name (FirstName, LastName, SortingName, MiddleName, Name)

Employee Job Title (JobID)

Employee Starting and Ending Dates

Org Structure:  Org Number, Org Name, Manager ID, StartDate, EndDate, PersonID

Hi All.

I am trying  convert the PPDS planned order to Production orders by activating conversion indicators and observed that either orders not transferred to ECC system or not converted  in APO system.

could plz what would be the reason  I have checked RFC connection it is fine and also forced to to send with t code /n/sapapo/cq but still not working.

thanks

Mohan 

Hello All,

I have created a Stacked Area chart as seen in the screenshot below that has the User_Name on the X-axis and Average of Productivity on Y-Axis.

In my record selection I have Date = LastFullWeek and hence this chart is for the past week only.

Is there any way for the graph to also show data for the past month and yesterday for each user on the same chart?

Is there any better graphical tool than stacked area chart that can be utilized to show the users productivity for yesterday, past week and past month respectively?

I would greatly appreciate any response.

Thanks.

What middleware is needed to send data from SAP ERP to C4C?  Is it better to us PI or HCI?

We are currently working on Employee Replication and need to update both the Employee Record with current information including Job Title.  Additionally, we need to update the Org Structure to ensure that manager is related appropriately.

We are using SuccessFactors for the employee Software.

Hi All,

I want to understand how the internal table TKOMP[] is populated in subroutine PRUEFEN in program SAPLMEPO. Am trying to run ME59N (Convert purchase requisition to PO) and in the FM MEPO_DOC_CHECK the subroutine PRUEFEN is being called.  Till I enter this subroutine the table tkomp remains invalid and as soon as I enter into PRUEFEN subroutine it becomes valid and already filled with a row.

I tried system debugging and everything I can think of but still cannot determine where this table TKOMP is being populated.  Is there anyone encountered the same issue ? I saw a thread in SCN but that is unanswered and there is not much help.

It would be great if anyone give some insights into this. Am getting error because of BRTWR(Gross volume) field in this structure. We have checked the inforecord and everything seems fine. Have to figure out where is this value coming in . Please help.

Thanks

Nagaraj Ashwath